The outcome of a "mvn install" is the following:
$ ls src/main/java/__ds_archive
com junit META-INF org
$ ls src/main/java/__cp_archive
com META-INF
As you can see from above, the 2 extra junit packages have been unpacked
in the case of __ds_archive from nowhere. The dependencies mentioned in
the dependencies list does not have a transitive dependency on junit
also. Even then, it has been unpacked.
Brian E. Fox wrote:
What happens for the subsequent executions? Can you paste your pom? Why
do you have multiple executions? The unpack-dependencies can take a list
of dependencies and each one can be unpacked into different folders (the
output directory is configurable at the artifactItem level too)
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 18, 2008 3:10 PM
To: [email protected]
Subject: Using the maven-dependency-plugin
Hi,
I am using the maven-dependency-plugin "unpack-dependencies" to unpack
the dependencies into some directory in my target directory. When i have
multiple executions, the first unpack-dependencies execution unpacks the
junit jar by default into my output directory. This does not happen for
the subsequent executions. Any ideas why this happens?
I have enabled the <excludeTrasitive> flag.
Thanks,
Shalini.
---------------------------------------------------------------------
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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]