I'm not agree: I hope that the classpath on maven should be the same
that the classpath given to antrun plugin.
It's probably true that what i am doing is dirty, but we are massively
migrating projects to maven (~400 projects), and we can't write a clean
pom for each one, this will be done progressively.
Benoit
VUB Stefan Seidel wrote:
Hi,
I think it is perfectly normal for any java program to ignore any
non-java files (like tgz) in the classpath or not to add them even if
requested. Maybe you should rather use another plugin (like
dependency-plugin) to extract the tgz into the target/classes or a
similar folder?
Stefan
Benoit Decherf wrote:
Hi,
I have a problem with the classpath passed to antrun:
If my project have a compile dependency on a tgz, the tgz doesn't
appear in the maven.compile.classpath.
I attache the example that reproduce the bug:
In project A, just execute mvn install. It create several artifacts :
A.jar A-jar-with-dependencies.jar, A.tar.bz2, etc...
In project B:
mvn dependency:tree show all the dependencies
mvn compile just execute the antrun plugin and print the classpath.
Can you confirm me that there is a bug ?
Is there a workaround on this bug ?
Benoit
------------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
