[MNG-1024] Reactor does not allow multiple plugin versions across projects

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 2.0-beta-1
• Component/s: Plugins and Lifecycle, Reactor and Workspace
• Assignee: John Dennis Casey
• Reporter: Mike Perham
• Created: 26/Sep/05 17:56
• Updated: 12/Mar/08 14:40
• Resolved: 12/Mar/08 14:40

Description

I have a multiproject build which has the following dependency tree:

top

• storage
• xdoclet plugin
• antrun plugin 1.0-alpha-1
• core
• antrun plugin 1.0-alpha-2

When I run the build for storage and core by themselves, everything is groovy.
When I run the top-level build, the storage build and xdoclet plugin run just great but the core build fails with the following message:

[ERROR] Nonexistent component: org.apache.maven.plugin.Mojoorg.apache.maven.plugins:maven-antrun-plugin:1.0-alpha-1:run

I am assuming there is some problem with multiple versions of the same plugin and the reactor but it certainly could be something I am missing in my pom. Here's how core is defining the plugin:

<build>
<pluginManagement>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-antrun-plugin</artifactId>
<version>1.0-alpha-2-SNAPSHOT</version>
...

Issue Links

• relates to: MNG-3284 Cached plugins are used, even when the specifically declared
• relates to: MNG-1949 project-level plugin dependencies not handled correctly in multimodule builds