Hi,
I'm a bit unhappy with Maven's dependency conflict resolution (as of 2.0.6
at least), which results in surprising version downgrades, multiple
versions of the same dependency, and other unpleasant effects. Example: a
WAR project depends on commons-configuration:1.4, which has these
On 06/06/07, Klaus Brunner [EMAIL PROTECTED] wrote:
Hi,
I'm a bit unhappy with Maven's dependency conflict resolution (as of 2.0.6
at least), which results in surprising version downgrades, multiple
versions of the same dependency, and other unpleasant effects. Example: a
WAR project depends on
This shouldn't happen if you're clean packaging.
Not sure what you mean by clean packaging. I can reproduce this problem
with a simple mvn clean install run - both JAR versions end up in the
WEB-INF/lib directory. The commons-xxx JARs are straight from the central
repository.
The default
On 06/06/07, Klaus Brunner [EMAIL PROTECTED] wrote:
This shouldn't happen if you're clean packaging.
Not sure what you mean by clean packaging. I can reproduce this problem
with a simple mvn clean install run - both JAR versions end up in the
WEB-INF/lib directory. The commons-xxx JARs are
