Plugin Configuration from Grandparent Not Executed on Grandchild
----------------------------------------------------------------
Key: MNG-5174
URL: https://jira.codehaus.org/browse/MNG-5174
Project: Maven 2 & 3
Issue Type: Bug
Components: Inheritance and Interpolation
Affects Versions: 3.0.2
Environment: ava version: 1.6.0_24, vendor: Apple Inc.
Default locale: en_US, platform encoding: MacRoman
OS name: "mac os x", version: "10.6.7", arch: "x86_64", family: "mac"
Reporter: Lon Binder
Priority: Blocker
Attachments: build.log
Summary: The configuration of a plugin in the grandparent of a project, whether
in <plugins> or <pluginManagement> is not properly inherited to grandchild.
To reproduce:
Setup:
POM C extends POM B; POM B extends POM A
POM A includes:
{code}
...
<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-dependency-plugin</artifactId>
<version>2.3</version>
<executions>
<execution>
<id>copy-dependencies</id>
<phase>package</phase>
<goals>
<goal>copy-dependencies</goal>
</goals>
<configuration>
<outputDirectory>${project.build.directory}/dependency-libs</outputDirectory>
</configuration>
</execution>
</executions>
</plugin>
</plugins>
</build>
...
{code}
Then in the POM C folder execute {{mvn package}}. The plugin does not work.
If the same configuration is moved or copied to POM B, then the execution in
POM C's folder is repeated, it works fine.
The same holds true if the above is moved to POM A's {{<pluginManagement>}}
node (and the appropriate {{<plugin>}} groupId and artifactId are added to POM
C). It even holds true if you do this and add additional to POM B. Unless the
full config is in POM B (or POM C) then it will not run from POM C.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
