My team needs to get rid of classes in a large application that are no
longer used. There are around 1500 class files in total and we estimate
that about 25% of these classes are no longer used. Is there some type
of tool that can identify classes that have been run during a certain
time period or some way to identify these classes other then removing
them from a build and getting compliation errors? We are using Eclipse
as a development tool and Tomcat as a server.
Ferenc Hechler - 21 Aug 2006 22:17 GMT
wgblackmon@yahoo.com schrieb:
> My team needs to get rid of classes in a large application that are no
> longer used. There are around 1500 class files in total and we estimate
[quoted text clipped - 4 lines]
> them from a build and getting compliation errors? We are using Eclipse
> as a development tool and Tomcat as a server.
You can try Autojar
http://autojar.sourceforge.net/
This application analyses the dependencies starting from one or
more classes.
I have integrated Autojar in the experimental beta release
of Fat-Jar Eclipse Plug-In:
http://kurucz-grafika.de/fatjar/beta/index.html
Best regards,
feri
Ira Baxter - 22 Aug 2006 22:42 GMT
> My team needs to get rid of classes in a large application that are no
> longer used. There are around 1500 class files in total and we estimate
[quoted text clipped - 3 lines]
> them from a build and getting compliation errors? We are using Eclipse
> as a development tool and Tomcat as a server.
Semantic Designs has a tool for removing "dead" (e.g., unreferenced)
code from a set of Java classes.
See http://www.semdesigns.com/Products/Tools.html

Signature
Ira Baxter, CTO
www.semanticdesigns.com