Affects Version/s: 2.1
Fix Version/s: None
Environment:OSX 10.6.2, java 1.6.0_17
Number of attachments :
I just introduced some qualifier for some libs that require to be compiled in java5.
I've been very confused when realizing that when packaging a webapp depending on those qualified artifacts, the non qualified versions are included instead.
It seems to come from dependency plugin.
Here is what happens:
When I do a dependency:tree on an artifact that depends directly on qualified libs, I get something regular:
The stageof lib depends on the jdk1.5 qualified commons and commons-xml libs.
When I do a dependency:tree on an upper level webapp that depends on this stageof lib:
it finds correctly the qualified version of stageof, but include non qualified commons and commons-xml.
These unqualified versions are the dependencies of the also non qualified stageof-1.4-SNAPSHOT.
From this behavior, I presume dependency plugin makes a mistake in looking from the wrong pom, probably not using the qualifier of the included dependency:
Hope this is clear.
I could provide an example if you can't reproduce easily.
Actually, just adding a qualifier to the jar-plugin to produce the artifact and to the <dependency> section should do the job.