You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2006/03/10 04:35:23 UTC
[jira] Commented: (MNG-2140) Mojo in forked lifecycle invoked in
reactor build cannot find reactor dependency
[ http://jira.codehaus.org/browse/MNG-2140?page=comments#action_60614 ]
Brett Porter commented on MNG-2140:
-----------------------------------
not blocking 2.0.3. It's not a regression.
The workaround is to "mvn install" instead of "mvn package". I'd suggest that the forked lifecycle is not cloning the list of already resolved projects and their locations.
> 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