You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org> on 2010/04/09 23:00:23 UTC

[jira] Closed: (MNG-4453) [regression] Plugin versions defined in a lifecycle mapping are not respected

     [ http://jira.codehaus.org/browse/MNG-4453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Benjamin Bentmann closed MNG-4453.
----------------------------------

       Resolution: Fixed
    Fix Version/s: 3.0-beta-1
         Assignee: Benjamin Bentmann

Fixed in [r932609|http://svn.apache.org/viewvc?view=revision&revision=932609].

> [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 & 3
>          Issue Type: Bug
>          Components: Plugins and Lifecycle
>    Affects Versions: 3.0-alpha-4
>            Reporter: Benjamin Bentmann
>            Assignee: Benjamin Bentmann
>             Fix For: 3.0-beta-1
>
>
> 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