Maven 2 & 3

Mojo in forked lifecycle invoked in reactor build cannot find reactor dependency

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 2.0.2
  • Fix Version/s: 3.0-alpha-3
  • Component/s: Reactor and workspace
  • Labels:
    None
  • Complexity:
    Intermediate
  • Testcase included:
    yes
  • Number of attachments :
    1

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

Bug - A problem which impairs or prevents the functions of the product. MNG-1682 Plugins do not honor the correct extension when run as a part of a multiproject build

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Brett Porter added a comment -

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.

Show
Brett Porter added a comment - 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.
Hide
Permalink
Walco van Loon added a comment -

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.

Show
Walco van Loon added a comment - 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.
Hide
Permalink
Guillaume Duchesneau added a comment -

I am using the Cobertura plugin and as Walco said in its comment, it is not very convenient to install all modules prior to launching the tests for code coverage...

To understand what was going on behind the scene in Maven, I wrote two simple test mojos : one that forks the lifecycle and one that does not. I found out that the field projectReferences in the class org.apache.maven.project.MavenProject is not set when forking the lifecycle causing the artifact resolution to fail for project in the reactor not yet installed. I (maybe naively) think that the problem is simply due to the fact that the copy constructor in MavenProject does not copy that field. I used Maven 2.0.4 sources to step in the code.

I hope this can help...

Show
Guillaume Duchesneau added a comment - I am using the Cobertura plugin and as Walco said in its comment, it is not very convenient to install all modules prior to launching the tests for code coverage... To understand what was going on behind the scene in Maven, I wrote two simple test mojos : one that forks the lifecycle and one that does not. I found out that the field projectReferences in the class org.apache.maven.project.MavenProject is not set when forking the lifecycle causing the artifact resolution to fail for project in the reactor not yet installed. I (maybe naively) think that the problem is simply due to the fact that the copy constructor in MavenProject does not copy that field. I used Maven 2.0.4 sources to step in the code. I hope this can help...

People

  • Assignee:
    Benjamin Bentmann
    Reporter:
    Grzegorz Slowikowski
Vote (1)
Watch (2)

Dates

  • Created:
    Updated:
    Resolved: