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

Sascha Scholz edited comment on MNG-4453 at 5/31/10 9:06 AM:
-------------------------------------------------------------

Benjamin's fix for Maven 3.0-beta-1 removes several (why not all?) plugins from 
the pluginManagement section in the Maven super POM. Instead, packaging type 
specific artifact handlers are used. But of course this is done only for 'core' 
packaging types. For others the latest plugin version is used (e.g. for 
nexus-plugin packaging type). I think that's a critical regression because not 
all builds are reproducable any more.

      was (Author: zlosch):
    Benjamin's fix for Maven 3.0-beta-1 removes several (why not all?) plugins 
from the pluginManagement section in the Maven super POM. Instead, packaging 
type specific artifact handlers are used. But of course this is done for 'core' 
packaging types. For others the latest plugin version is used (e.g. for 
nexus-plugin packaging type). I think that's a critical regression because not 
all builds are reproducable any more.
  
> [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/[email protected]/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

        

Reply via email to