Gilles Scokart wrote on 10/08/2008 09:40 AM:
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?
You could try something like AutoJar
(http://sourceforge.net/projects/autojar/ ) to do bytecode analysis of
class dependencies, and then identify the jars required to satisfy
those dependencies. I could see a workable ant task being created from
such a technique.
Thanks,
--kirby
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
