[ 
http://jira.codehaus.org/browse/MNG-3394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_124056
 ] 

Benjamin Bentmann commented on MNG-3394:
----------------------------------------

bq. I think this is intended behaviour
Oh please not. What would be the rationale for that? If a user explicitly 
declares a {{<version>}} element under {{<build>.<plugins>}} isn't that a clear 
indication of this intention to use that version? Do you want to explain to 
users why that is ignored and they need to hassle with setting up a 
{{<pluginManagement>}} entry just for the fun of overriding a plugin version 
inherited from the parent? Do you want to clarify why the little sentence 
"Plugin Management contains plugin elements in much the same way, except that 
*rather than configuring plugin information for this particular project* build, 
it is intended to configure project builds that inherit from this one." that 
users learned from http://maven.apache.org/pom.html#Plugin_Management is not 
quite up with the reality?

Last but not least, the lack to override the version only manifest itself
a) for a lifecycle phase, not for a direct mojo invocation
b) only for the first lifecycle phase

bq. what if you change the pluginManagement of child modules?
As I already commented in the attached demo POMs, this successfully allows the 
childs to change the version.

> 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

        

Reply via email to