[jira] Commented: (MNG-2140) Mojo in forked lifecycle invoked in reactor build cannot find reactor dependency

["Walco van Loon (JIRA)" <ji...@codehaus.org>]

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

Walco van Loon commented on MNG-2140:
-------------------------------------

Like the original reporter, I think it's important to fix this issue, because it will prevent plugins like Cobertura and Clover to run in a multi project build if the modules have interdependencies. For these plugins, the suggested workaround is not really convenient, as they are supposed to execute in a phase prior to the install phase.

> Mojo in forked lifecycle invoked in reactor build cannot find reactor dependency
> --------------------------------------------------------------------------------
>
>          Key: MNG-2140
>          URL: http://jira.codehaus.org/browse/MNG-2140
>      Project: Maven 2
>         Type: Bug

>   Components: Reactor and workspace
>     Versions: 2.0.2
>     Reporter: Grzegorz Slowikowski
>  Attachments: test.zip
>
>
> In multiproject I have two modules. One of them (lets name it "main") depends on the second one ("util").
> If I bind forking lifecycle mojo in the "main" artifact pom, that mojo does not find "util" artifact and tries to find it in local and remote repositories.
> If the same mojo does not for lifecycle, reactor build finishes with success.
> I attach an example:
> - plugin with two mojos writing something to the log, one of them forks lifecycle, second - does not
> - test multiproject using test mojo
> There are some plugins forking lifecycles, so I think this can be serious problem.
> I would love to see its priority to "Blocker" for Maven 2.0.3

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