Env: JDK1.6, Maven 2.0.7
I have projects TOP, A1, A12 and A13 structured as follows:
(TOP
(A1
(A11) (A12) (A13)
)
)
A11 and A12 generate jarartifacts. A13 generates war artifact and depends on
A11 and A12:
A13 => A12
A12 => A11
Somehow A13.war needs a third-party jar artifact "foo.jar" which would be
"provided" by the servlet container using commons loader. Hence I
have inserted the dependency in TOP project as well as A13:
<dependency>
<group>foo</group>
<artifactId>foo</artifactId>
<version>1.0</version>
<scope>provided</provided>
</dependency>
However, the war artifact generated by A13 still contains foo-1.0.jar.
Effective POM of A13 contains only one dependency for foo.jar which is
listed
above (provided):
$ cd TOP/A1/A13
$ mvn help:effective-pom
//...
<dependency>
<group>foo</group>
<artifactId>foo</artifactId>
<version>1.0</version>
<scope>provided</provided>
</dependency>
//...
$
Then how can A13.jar contain foo-1.0.jar? How can I force A13
to skip packaging foo-1.0.jar?
Also, how do I trace transitive dependency? Meaning, is there a
plugin which would go from the leaf to the parent artifact that is
triggeriing the inclusion of foo-1.0.jar? Example:
$ cd TOP/A1/A13
$ mvn trace-lineage:trace-lineage -Dgroup=foo -artifactId=foo
-Dversion=1.0
//...
foo-1.0.jar required by bar-1.0.jar
bar-1.0.jar required by adam-1.0.jar
adam-1.0.jar required by god-1.0.jar
$
So I could say "Aha! God is triggering foo to be included"/
Please help!
Thanks,
/U
--
View this message in context:
http://www.nabble.com/Tracing-transitive-dependeny---please-help%21-tp14551703s177p14551703.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
