maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paul Benedict (JIRA)" <j...@codehaus.org>
Subject [jira] Commented: (MNG-4453) [regression] Plugin versions defined in a lifecycle mapping are not respected
Date Wed, 18 Nov 2009 13:15:55 GMT

    [ http://jira.codehaus.org/browse/MNG-4453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=198611#action_198611
] 

Paul Benedict commented on MNG-4453:
------------------------------------

>> Second, I always subscribe to the theory that "closest" wins.

It's more than a theory. It's documented on Maven's web site it's the only resolution strategy
it currently supports.

> [regression] Plugin versions defined in a lifecycle mapping are not respected
> -----------------------------------------------------------------------------
>
>                 Key: MNG-4453
>                 URL: http://jira.codehaus.org/browse/MNG-4453
>             Project: Maven 2
>          Issue Type: Bug
>          Components: Plugins and Lifecycle
>    Affects Versions: 3.0-alpha-4
>            Reporter: Benjamin Bentmann
>
> As reported by Sebastian Annies in [Using a specific plugin version in custom lifecycle|http://www.mail-archive.com/dev@maven.apache.org/msg82871.html],
the plugin version given by a lifecycle mapping like
> {code:xml}
> <verify>org.apache.maven.plugins:maven-source-plugin:2.1:jar-no-fork</verify>
> {code}
> is not respected by Maven 3.0, it's preferring the version from the plugin management
of the super POM instead.

-- 
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