<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Why Use a Sledgehammer When There is a Bulldozer Lying Around</title>
	<atom:link href="http://www.rojotek.com/blog/2007/10/17/why-use-a-sledgehammer-when-there-is-a-bulldozer-lying-around/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.rojotek.com/blog/2007/10/17/why-use-a-sledgehammer-when-there-is-a-bulldozer-lying-around/</link>
	<description>Software Development in Brisbane</description>
	<lastBuildDate>Fri, 03 Feb 2012 20:00:10 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.3</generator>
	<item>
		<title>By: JWhich in a line of code - Rob@Rojotek</title>
		<link>http://www.rojotek.com/blog/2007/10/17/why-use-a-sledgehammer-when-there-is-a-bulldozer-lying-around/comment-page-1/#comment-17722</link>
		<dc:creator>JWhich in a line of code - Rob@Rojotek</dc:creator>
		<pubDate>Wed, 20 Aug 2008 04:35:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.rojotek.com/blog/2007/10/17/why-use-a-sledgehammer-when-there-is-a-bulldozer-lying-around/#comment-17722</guid>
		<description>[...] Old skool java programmers will have almost certainly come across the tool JWhich (http://www.javaworld.com/javaworld/javatips/jw-javatip105.html). &#160;It&#039;s the classic tool for finding out which jar file contains a class. &#160;The following line of code has the same effect, and is slightly better than just trying to grep jar files. [...]</description>
		<content:encoded><![CDATA[<p>[...] Old skool java programmers will have almost certainly come across the tool JWhich (<a href="http://www.javaworld.com/javaworld/javatips/jw-javatip105.html" rel="nofollow">http://www.javaworld.com/javaworld/javatips/jw-javatip105.html</a>). &#160;It&#39;s the classic tool for finding out which jar file contains a class. &#160;The following line of code has the same effect, and is slightly better than just trying to grep jar files. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Graham Bucknell</title>
		<link>http://www.rojotek.com/blog/2007/10/17/why-use-a-sledgehammer-when-there-is-a-bulldozer-lying-around/comment-page-1/#comment-13372</link>
		<dc:creator>Graham Bucknell</dc:creator>
		<pubDate>Fri, 14 Mar 2008 06:02:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.rojotek.com/blog/2007/10/17/why-use-a-sledgehammer-when-there-is-a-bulldozer-lying-around/#comment-13372</guid>
		<description>Hi,

I have a similar method to you (also slegehammer-ey) but it works. I have a script called superfind.sh - if I need to know where a class is,  I just cd to the top of a likely directory tree and go superfind.sh  and it will print out all the classes found.

#!/bin/bash

find . -type f -print0 &#124; xargs -0 grep -l &quot;$1&quot;</description>
		<content:encoded><![CDATA[<p>Hi,</p>
<p>I have a similar method to you (also slegehammer-ey) but it works. I have a script called superfind.sh &#8211; if I need to know where a class is,  I just cd to the top of a likely directory tree and go superfind.sh  and it will print out all the classes found.</p>
<p>#!/bin/bash</p>
<p>find . -type f -print0 | xargs -0 grep -l &#8220;$1&#8243;</p>
]]></content:encoded>
	</item>
</channel>
</rss>

