[Clirr-devel] Analysing jarfiles without dependencies

[Simon K. <ski...@ap...>]

Hi Lars,

I see you're doing some updates at the moment. Before a new release is 
made, there is one thing that it would be great to fix (I've been trying 
to get around to it for months now :-).

The previous version of clirr could generate a report without needing 
the full set of dependencies for a project, eg code that is all in 
package "example.acme.widget" can be compared against the previous 
version without needing third-party jars such as org.apache.commons.io, 
etc. With the rewrite from BCEL to ASM this ability appears to have been 
lost. Projects that use clirr via maven won't notice a problem as maven 
can pass all the dependencies to clirr easily - but people doing their 
own analysis on differences in a third-party jar will find things more 
difficult.

Just wanted to point this out..

Regards, Simon