[MNG-2140] Mojo in forked lifecycle invoked in reactor build cannot find reactor dependency

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0.2
• Fix Version/s: 3.0-alpha-3
• Component/s: Reactor and Workspace
• Assignee: Benjamin Bentmann
• Reporter: Grzegorz Slowikowski
• Created: 09/Mar/06 12:41
• Updated: 30/Jul/09 13:07
• Resolved: 30/Jul/09 13:07

Description

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

Issue Links

• relates to: MNG-1682 Plugins do not honor the correct extension when run as a part of a multiproject build