[
http://jira.codehaus.org/browse/MNG-3394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_126380
]
John Casey commented on MNG-3394:
---------------------------------
The problem seems to be coming from the
DefaultLifecycleExecutor.getMojoDescriptor(..) method. After parsing or
otherwise acquiring a Plugin object for the task being invoked, it blindly
injects pluginManagement values without first checking the project for a
matching non-pluginManagement plugin entry...then, it passes the plugin off to
the DefaultPluginManager.verifyPlugin(..) method, which from what I can tell
would have done this in the correct order (including the
project/build/plugins/plugin info over the pluginManagement info).
I'm currently trying to figure out whether we can remove the
project.injectPluginManagementInfo(..) call from
DefaultLifecycleExecutor.getMojoDescriptor(..), to simplify things and restore
some semblance of sanity. ;-)
> Plugin versions inherited via <pluginManagement> cannot be overriden by
> <build>.<plugins> section of sub modules
> ----------------------------------------------------------------------------------------------------------------
>
> Key: MNG-3394
> URL: http://jira.codehaus.org/browse/MNG-3394
> Project: Maven 2
> Issue Type: Bug
> Components: Inheritance and Interpolation
> Affects Versions: 2.0.8
> Reporter: Benjamin Bentmann
> Priority: Critical
> Fix For: 2.0.9
>
> Attachments: plugin-management-version.zip
>
>
> See the comments in the module POM of the attached demo project for more
> explanation.
--
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
