[MNG-2174] <pluginManagement><plugins><plugin><dependencies> do not propogate to child POM plugins (potentially scoped to only affecting child POM plugins that live within a <profile>)

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.0.9, 2.1.0-M1, 3.0-alpha-3
• Component/s: Inheritance and Interpolation, Plugins and Lifecycle
• Assignee: Britton Isbell
• Reporter: skaze
• Created: 23/Mar/06 07:00
• Updated: 10/Feb/09 16:37
• Resolved: 09/Feb/09 10:07

Description

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

Issue Links

• is duplicated by: MNG-2946 Module-by-Profile seems to break plugin dependencies
• is related to: MNG-1703 <pluginManagement><dependencies> is not propagated to child POMs
• is related to: MNG-3725 Cannot override plugin dependencies in maven 2.0.9