ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "McHenry, Matt" <>
Subject RE: Tool to find unused methods
Date Fri, 05 Apr 2002 23:38:47 GMT
(Sorry if this is a bit out of date ... I'm a bit backlogged in my reading
of this list.)

I've been using a tool called juliet for a few weeks now, and I like it
quite a bit.  You can get it at  It's a
GUI-based tool for browsing source code.  So you can give it the name of a
class, field, or method and it will show you all the places where it's used,
overridden, etc.  As discussed elsewhere it will not detect usages via
reflection, but it does find just about everything else.  (There is no ant

The free version is crippled in one respect: if you edit the source files
it's looking at, it stops working & you have to restart it.  That has turned
out not to be a big deal for me.

Matt McHenry
Software Developer
Carnegie Learning

> -----Original Message-----
> From: Scott Ellsworth []
> Sent: Monday, March 25, 2002 13:33
> To: Ant Users List
> Subject: Re: Tool to find unused methods
> On Monday, March 25, 2002, at 08:26  AM, Dominique Devienne wrote:
> > In the question at hand, it was more to remove dead code than to 
> > package a lean Java app anyway. --DD
> Exactly.  My hope was to send in a couple of classes that I 
> am currently 
> suspicious of, and to get a usage report.  If functions are 
> unused, then 
> I still have to do the manual step of (for example) making sure that 
> these are not implementations of functions in parent classes and the 
> like, but at least I have some place to start.
> Dead code analysis is always fun to perform, and anything 
> that makes it 
> less tedious is a win.
> Scott

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message