Brian Fox (JIRA)
Tue, 17 Nov 2009 18:25:28 -0800
[
http://jira.codehaus.org/browse/MNG-4453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=198582#action_198582
]
Brian Fox commented on MNG-4453: -------------------------------- Personally I didn't even know you could put a version into the lifecycle, I've never seen that done. Second, I always subscribe to the theory that "closest" wins. In the inheritance case, it means things in my pom override my parent pom, which overrides the grandparent etc. I think in this case, the pom is "closer" than the lifecycle and therefore it should win as is happening in the 3.x case. In otherwords, if I use a lifecycle that defines a version but need to tweak the version how would I do it? The pom is my only vechicle for overriding it. > [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/d...@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