maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nathan Coast (JIRA)" <j...@codehaus.org>
Subject [jira] Commented: (MASSEMBLY-393) Cannot Override dependencyManagement
Date Fri, 11 Sep 2009 17:03:32 GMT

    [ http://jira.codehaus.org/browse/MASSEMBLY-393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=190639#action_190639
] 

Nathan Coast commented on MASSEMBLY-393:
----------------------------------------

confirmed, exact same issue - dependency plugin reports correct overridden version.  assembly
plugin uses incorrect version from parent dependency management

> Cannot Override dependencyManagement
> ------------------------------------
>
>                 Key: MASSEMBLY-393
>                 URL: http://jira.codehaus.org/browse/MASSEMBLY-393
>             Project: Maven 2.x Assembly Plugin
>          Issue Type: Bug
>    Affects Versions: 2.2-beta-3
>         Environment: maven 2.0.9,2.0.10, windows xp, debian gnu linux, solaris 10
>            Reporter: deckrider
>         Attachments: my-app-pom-packaging.zip, my-app.zip
>
>
> 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.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message