[ http://jira.codehaus.org/browse/MNG-2174?page=comments#action_69944 ] Brett Porter commented on MNG-2174: -----------------------------------
this needs to be checked from an inheritence perspective, but there's also a chance that it's just a victim of the bug where only plugin dependencies from the first POM activating the plugin are taken (which is a more complicated fix as it pertains to how the plugin classloader is constructed). In both cases, the workaround is to put the plugins with dependencies in the root POM. > <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.0.5 > > > <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
