Multiple Inheritence causes plugin executions to run multiple times (Test Case Attached)

Further investigation using help:effective-pom shows that the plugin configuration actually gets included 2x in the pom. Shouldn't executions with the same name be merged with their parent?

I verified in my sample and in my real project that this appears to be fixed in 2.0.3. The fixed version should be updated so that the JIRA report reflects the correct information. I'd like to see this get created as an integration test to prevent future regresion, but I'm not 100% sure how to test for this condition.

confirmed fixed by Brian Fox, I just added a variant of sample.zip as it0096.

There was some regression on this issue between the RC and the final version. In 2.0.2, the sample ran the sources jar 3 times. In 2.0.3 RC, it ran only once (correct). In 2.0.3 final it now runs 2 times:

[INFO] Installing E:\svn\dsms-2.1\legacy\hl7\target\hl7-2.1.0.7-SNAPSHOT.jar to
e:\stc\mavenRepo\com\stchome\products\dsms\legacy\hl7\2.1.0.7-SNAPSHOT\hl7-2.1.0
.7-SNAPSHOT.jar
[INFO] Installing E:\svn\dsms-2.1\legacy\hl7\target\hl7-2.1.0.7-SNAPSHOT-sources
.jar to e:\stc\mavenRepo\com\stchome\products\dsms\legacy\hl7\2.1.0.7-SNAPSHOT\h
l7-2.1.0.7-SNAPSHOT-sources.jar
[INFO] Installing E:\svn\dsms-2.1\legacy\hl7\target\hl7-2.1.0.7-SNAPSHOT-sources
.jar to e:\stc\mavenRepo\com\stchome\products\dsms\legacy\hl7\2.1.0.7-SNAPSHOT\h
l7-2.1.0.7-SNAPSHOT-sources.jar

Brian,

Can you tell me what the key difference is between your project above (dsms-2.1, looks like?) and it0096, which is based on the sample.zip?

I just re-downloaded sample.zip, and it works fine on this side (running with a copy of mvn I downloaded this morning).

Brian, also please detail exactly which RC you are using (time/date). I don't believe anything was changed between the last one and the release.

I was running with 2.0.3-SNAPSHOT that was built on March 2nd. I believe this was one of the earlier RCs.

I also noticed that the sample seems to work even though it was based on my original project, which doesn't work. I'll go back and see if I can figure out the difference.

Apparently the only difference is the number of levels between the plugin definition to the child. This updated sample now produces 3 or more executions of the sources jar

The only difference between this version and the previous sample is an additional inheritence level.

This test shows multiple calls of the same goals. Try 'mvn clean', 'mvn generate-sources', 'mvn package'.
It contains a parent and a child pom, and when run from the parent pom there are multiple executions of the same
goals:

$ mvn -version
Maven version: 2.0.4-SNAPSHOT

(http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/m2-20060330.155710.tar.gz)

$ mvn clean

[INFO] Scanning for projects...
[INFO] Reactor build order:
[INFO] parent
[INFO] child
[INFO] ----------------------------------------------------------------------------
[INFO] Building parent
[INFO] task-segment: [clean]
[INFO] ----------------------------------------------------------------------------
[INFO] [clean:clean]
[INFO] Deleting directory /vol/home/forge/work/sandbox/m2test/antrun2/target
[INFO] Deleting directory /vol/home/forge/work/sandbox/m2test/antrun2/target/classes
[INFO] Deleting directory /vol/home/forge/work/sandbox/m2test/antrun2/target/test-classes
[INFO] [antrun:run

]
[INFO] Executing tasks
[echo] test2
[INFO] Executed tasks
[INFO] ----------------------------------------------------------------------------
[INFO] Building child
[INFO] task-segment: [clean]
[INFO] ----------------------------------------------------------------------------
[INFO] [clean:clean]
[INFO] Deleting directory /vol/home/forge/work/sandbox/m2test/antrun2/child/target
[INFO] Deleting directory /vol/home/forge/work/sandbox/m2test/antrun2/child/target/classes
[INFO] Deleting directory /vol/home/forge/work/sandbox/m2test/antrun2/child/target/test-classes
[INFO] [antrun:run

]
[INFO] Executing tasks
[echo] test2
[INFO] Executed tasks
[INFO] [antrun:run

]
[INFO] Executing tasks
[echo] childTest2
[INFO] Executed tasks
[INFO] [antrun:run

]
[INFO] Executing tasks
[echo] test2
[INFO] Executed tasks
[INFO] [antrun:run

]
[INFO] Executing tasks
[echo] childTest2
[INFO] Executed tasks
[INFO]
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO] ------------------------------------------------------------------------
[INFO] parent ................................................ SUCCESS [1.022s]
[INFO] child ................................................. SUCCESS [0.069s]
[INFO] ------------------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESSFUL
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1 second
[INFO] Finished at: Fri Mar 31 14:18:10 CEST 2006
[INFO] Final Memory: 2M/6M
[INFO] ------------------------------------------------------------------------

This does seem some how related, but it's not quite the same. The original problem I saw was just the executions defined in the parent got executed a bunch of times. In your case, some of the child executions are rerun too.

Kenney, please file a new bug.

I've filed http://jira.codehaus.org/browse/MNG-2221 which I think is the same as Kenney's.