On 26/10/2010 18:47, thomas wrote:
It usually happens in projects that dependencies are getting added to the
build.gradle file which later then don't get removed when the code gets
changed and the need for the dependency becomes superfluous.
Is there any reporting available that could be used to identify these cases?
Indirectly, you can use JBoss' Tattletale to analyze a bunch of jar files and find
dependencies (or lack of) between them.
The reports are quite detailed.
Not exactly what you look for (as it is an independent tool) but worth a look.
--
Philippe Lhoste
-- (near) Paris -- France
-- http://Phi.Lho.free.fr
-- -- -- -- -- -- -- -- -- -- -- -- -- --
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
