You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2006/07/17 08:08:24 UTC

[jira] Updated: (MNG-2174) do not propogate to child POM plugins (potentially scoped to only affecting child POM plugins that live within a )

     [ http://jira.codehaus.org/browse/MNG-2174?page=all ]

Brett Porter updated MNG-2174:
------------------------------

    Fix Version/s:     (was: 2.0.5)
                   2.1

moving out to 2.1. Even if the management inheritence is incorrect, fixing it won't help a great deal until the classloader construction is fixed

> <pluginManagement><plugins><plugin><dependencies> do not propogate to child POM plugins (potentially scoped to only affecting child POM plugins that live within a <profile>)
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: MNG-2174
>                 URL: http://jira.codehaus.org/browse/MNG-2174
>             Project: Maven 2
>          Issue Type: Bug
>            Reporter: John Allen
>             Fix For: 2.1
>
>
> <pluginManagement><plugins><plugin><dependencies> do not propogate to child POM plugins.
> Kenny believe this works OKAY if the childs are using the parent <pluginManagement> preconfigured plugins in their main <build> section however it does NOT work if the childs are trying to use those preconfigured plugins via their own <profiles>. Configuration propogates through okay but dependencies are missing and have to be respecified in the child POMs.

-- 
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