[MNG-2946] Module-by-Profile seems to break plugin dependencies

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 2.0.6
• Component/s: Dependencies
• Environment: jdk1.4
• Assignee: Brett Porter
• Reporter: Daniel Takai
• Created: 13/Apr/07 05:59
• Updated: 10/Feb/09 15:33
• Resolved: 18/Dec/08 07:10

Description

Using Module-by-Profile i ran into a problem with dependencies. My pom looks like this:

<profiles>
<profile>
<id>default</id>
<activation>
<activeByDefault>true</activeByDefault>
</activation>
<modules>
<module>module1</module>
<module>module2</module>
<module>module3</module>
</modules>
</profile>
<profile>
<id>integration</id>
<modules>
<module>module1</module>
<module>module2</module>
<module>module3</module>
<module>integration</module>
</modules>
</profile>
</profiles>

The integration module runs the integration tests.

The integration module contain an antrun plugin.

Running the build on the integration module only works fine.

Running it from the parent project using the integration profile breaks the build. The problem is that the plugin dependencies are not accessible to the ant build files (and therefore, i suppose, to the plugin).

Issue Links

• duplicates: MNG-1323 Plugin extensions (dependencies) not resolved in reactor build
• duplicates: 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>)