Comments on: Eclipse Papercut #3 – Plugin to find unused methods

By: Lars Vogel

Lars Vogel — Tue, 22 Dec 2009 17:29:20 +0000

@Amdee: Static methods which are called by the framework are currently reported as unused. You should have the same result if you select the method in Eclipse, right mouse click and select “Open Call Hierarchy”. To avoid this you could modify the code from me to analyse only non-static methods.

By: Amdee

Amdee — Mon, 21 Dec 2009 19:53:44 +0000

Lars,

To eliminate the obvious, I did ensure that the plugin was updated in my workspace. My log messages were showing up with the latest log messages.

Hope that helps,

-Amdee

By: Amdee

Amdee — Mon, 21 Dec 2009 19:51:48 +0000

Hi Lars,

Thanks for sharing your expertise on finding dead code. I am interested in builiding on it. to better understand how it works, I added the following helper method to Activator that logs to the Error log:

public static void info( String msg )
{
Status status = new Status(IStatus.OK, PLUGIN_ID, msg, null);
getDefault().getLog().log(status);
}

I recompiled and re-deployed the plugin and ran it on itself. I was surprised to see the Activator.getDefault() public static method reported as un-used. Any ideas?

Thanks,

Amdee

By: Lars Vogel

Lars Vogel — Wed, 09 Sep 2009 17:42:06 +0000

@Chaminda It should also work for standard Java projects in Eclipse. Give it a try and let me know if you face any issues.

By: Chaminda

Chaminda — Wed, 09 Sep 2009 15:14:13 +0000

Interesting, Nice article,

Can you give some hint to use your Code Analyzer outside of Eclipse,

I want to use this kind of thing in a Java class, Not within the Eclipse Plugin Project.

Any hint highly appreciate

Please be kind enough to make a copy to my mail as well

Thanks