Maven 2 & 3

[regression] Dependencies in forked reactor projects are not resolved when aggregator bound to lifecycle forks

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 3.0-beta-2
  • Fix Version/s: 3.0
  • Component/s: Plugins and Lifecycle
  • Labels:
    None
  • Complexity:
    Intermediate
  • Number of attachments :
    1

Description

Currently, dependency resolution happens only at the beginning of a project build and then only for the current project. This means if the current project happens to bind an aggregator into its lifecycle which forks the lifecycle in a reactor build, any forked project not previously built during the main build will have its dependencies unresolved.

Issue Links

is duplicated by

Bug - A problem which impairs or prevents the functions of the product. MSITE-497 Dependencies not included classpath for multi-level projects when forking reporting

  • Critical - Crashes, loss of data, severe memory leak.
  • 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
Benjamin Bentmann added a comment - - edited

Running "mvn package" from the top-level of the attached project fails with a compilation error due to missing dependency in the (forked) sub module.

Show
Benjamin Bentmann added a comment - - edited Running "mvn package" from the top-level of the attached project fails with a compilation error due to missing dependency in the (forked) sub module.
Hide
Permalink
Benjamin Bentmann added a comment -

Fixed in r996206.

Show
Benjamin Bentmann added a comment - Fixed in r996206 .

People

  • Assignee:
    Benjamin Bentmann
    Reporter:
    Benjamin Bentmann
Vote (1)
Watch (1)

Dates

  • Created:
    Updated:
    Resolved: