tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Konstantin Kolinko <>
Subject Re: svn commit: r783779 - /tomcat/trunk/java/org/apache/tomcat/util/buf/
Date Thu, 11 Jun 2009 16:13:21 GMT
2009/6/11 Mark Thomas <>:
> wrote:
>> Author: markt
>> Date: Thu Jun 11 14:16:49 2009
>> New Revision: 783779
>> URL:
>> Log:
>> Experiment with the UCDetector (Unused Code Detector) plug-in for Eclipse.
>> Remove all the code from the class that isn't used anywhere in Tomcat.
> Early indications are that this plug-in is going to find quite a bit of
> code that can de deleted or restricted in visibility.
> What are people's thoughts on running this over the entire code base?
> I would image that, if done, this would be done gradually, like the
> conversion to use generics.
> Mark

If you want to do it, then why not? It is your time to spend.

It is good to have some automated code review now before TC 7,
because it may be hard to fix some issues once it is released.

My experience with such tools is that you need to specify some
set of "entry points", including possible reflection calls and
classes specified through configuration, etc. and that may be hard.

I do not know how hard it will be with this tool, and how many
"// NO_UCD" comments [1] will be needed to dispose most of
false positives.  That will be your experience.


But, certainly, running a tool must be easier than doing manual

In one of my last projects I used coverage results to find unused code.
(Thanks to EclEmma plugin for Eclipse).
Those results, though require much more work, are more reliable.

Best regards,
Konstantin Kolinko

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message