When working on some big project with heavy history and when looking at the quality of some meta data in the maven repository I'm always shoked by the amount of useless dependencies used.
To counter that, I would like to use (and promote) a tool that help the developpers to limit their path to the strict minimum. I would like to start with the easiest : the compile path. (Next I would try to do the same for test classpath, and maybe for runtime classpath) I would like to push my build to an extreme solution. I want to make a build fail if some jars of the compile path are not used. Did you know a task that do that? Or did you know any tools that list the jars that are required by a sources (or a compiled jars) that I could adapt to make such a tasks? -- Gilles Scokart --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
