There are some things out there that will analyze source code and find what is used, but it is in general a hard problem as some packages are loaded at runtime based on properties. For example JSR232 loading of a scripting language or use of ehcache within hibernate. I don't think those types of dependencies could be picked up automatically by any tool as they are not directly listed in the source code anywhere.
My personal opinion is that you have to know your projects, and keep the dependencies pruned. I also like to have set my code up with many smaller projects in a larger multiproject with transitive dependencies so that you know project A gets depB from projectC because depB only appears in the build.gradle for projectC. But I am definitely guilty of leaving things in that are not used any more just due to laziness. Hard problem, no easy answers I suspect. Philip On Tue, Oct 26, 2010 at 12:47 PM, thomas <[email protected]> wrote: > > How does Gradle or Ivy help with unused dependencies? > > 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? > -- > View this message in context: > http://gradle.1045684.n5.nabble.com/Dependency-Analyzer-tp3237390p3237390.html > Sent from the gradle-user mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
