Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
2.2-beta-3
-
None
-
None
-
maven 2.0.9,2.0.10, windows xp, debian gnu linux, solaris 10
Description
This was not a problem in 2.2-beta-2.
I've provided a test case. It should produce a zip file containing log4j-1.2.14.jar but instead contains log4j-1.2.12.jar
To run the test case:
unzip my-app.zip
cd my-app.zip
mvn clean package
This is critical for us, because we have a master parent pom where we keep all our versions in a dependencyManagement section, but on occasion we want to override them. Upgrading from 2.2-beta-2 to 2.2-beta-3 broke that ability.
Attachments
Attachments
Issue Links
- is duplicated by
-
MASSEMBLY-247 versions of included dependencies in multi-module projects are not deterministic
- Closed
-
MASSEMBLY-299 assembly does not honnor <dependencyManagement> directives
- Closed
-
MASSEMBLY-432 assembly misapplies depMgt and selects the wrong dependency for an archive
- Closed
- is related to
-
MASSEMBLY-235 dependencySet ignores dependency management
- Closed