[ http://jira.codehaus.org/browse/MNG-1024?page=comments#action_49192 ] 

Jerome Lacoste commented on MNG-1024:
-------------------------------------

My findings, so far . I have a multiproject with following modules

core
clients
webapp
full-webapp
standalone

executed in that order

It only fails when using the reactor when trying to build the webapp module.

It tries to find the war-plugin v 2.0-beta-2 while the 2.0-beta-3-SNAPSHOT was 
(I think) to be searched.

[DEBUG] 
org.apache.maven.plugins:maven-war-plugin:maven-plugin:2.0-beta-3-SNAPSHOT 
(selected for runtime)
[DEBUG]   org.codehaus.plexus:plexus-utils:jar:1.0.4 (selected for runtime)
[...]
[DEBUG]   org.apache.maven:maven-artifact:jar:2.0 (selected for runtime)
[DEBUG]     org.codehaus.plexus:plexus-utils:jar:1.0.4 (selected for runtime)
[ERROR] Nonexistent component: 
org.apache.maven.plugin.Mojoorg.apache.maven.plugins:maven-war-plugin:2.0-beta-2:war

At this point, in DefaultLifeCycleEditor:

    private void executeGoal( String task, MavenSession session, MavenProject 
project )
        throws LifecycleExecutionException, BuildFailureException
    {
        try
        {
            if ( getPhaseToLifecycleMap().containsKey( task ) )
            {
                Lifecycle lifecycle = getLifecycleForPhase( task );

                // we have a lifecycle phase, so lets bind all the necessary 
goals
                Map lifecycleMappings = constructLifecycleMappings( session, 
task, project, lifecycle );
                executeGoalWithLifecycle( task, session, lifecycleMappings, 
project, lifecycle );

the lifecycle mappings are already wrong. They map to the beta-2 version. Now 
investigating the lifecyclemapping construction.

Handy breakpoints :)

> Reactor does not allow multiple plugin versions across projects
> ---------------------------------------------------------------
>
>          Key: MNG-1024
>          URL: http://jira.codehaus.org/browse/MNG-1024
>      Project: Maven 2
>         Type: Bug
>     Versions: 2.0-beta-1
>     Reporter: mike perham
>      Fix For: 2.1

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

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to