Maven 2 & 3

Classpath in reactor builds differ from dependency resolution

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Blocker Blocker
  • Resolution: Duplicate
  • Affects Version/s: 2.0.4
  • Fix Version/s: 2.0.5
  • Component/s: Reactor and workspace
  • Labels:
    None
  • Complexity:
    Intermediate
  • Number of attachments :
    1

Description

The classpath used to compile and test a module is wrong, if the module uses a released version of another module in the reactor build. If the module is build locally, the correct depednencies are on the classpath. This currently breaks our complete development and results makes e.g. EJBs useless (MEJB-18).

Issue Links

duplicates

Bug - A problem which impairs or prevents the functions of the product. MNG-1245 Reactor projects sometimes used even with version mismatch

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

Bug - A problem which impairs or prevents the functions of the product. MEJB-18 Manifest classpath contains wrong entries in multi-module build

  • Blocker - Blocks development and/or testing work, production could not run
  • 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
Jörg Schaible added a comment -

Attachment contains thw same minimal project in two steps. To demonstrate the poroblem run in step-1 "mvn install" and then do the same in step-2. You will see the unit test of the issue-client in step-2 failing. Go to the issue-client and run "mvn clean install" and the build has no problems. The problem in step 2 is the undesired usage of the SNAPSHOT version of "issue-core" in the classpath, although it is nowhere referenced. The client never stopped to demand the released version created in step-1.

Show
Jörg Schaible added a comment - Attachment contains thw same minimal project in two steps. To demonstrate the poroblem run in step-1 "mvn install" and then do the same in step-2. You will see the unit test of the issue-client in step-2 failing. Go to the issue-client and run "mvn clean install" and the build has no problems. The problem in step 2 is the undesired usage of the SNAPSHOT version of "issue-core" in the classpath, although it is nowhere referenced. The client never stopped to demand the released version created in step-1.
Hide
Permalink
Jörg Schaible added a comment -

Might be related to MNG-1245

Show
Jörg Schaible added a comment - Might be related to MNG-1245
Hide
Permalink
Jörg Schaible added a comment -

This is just another result of the problem described in MNG-1245. That fix solves also this issue.

Show
Jörg Schaible added a comment - This is just another result of the problem described in MNG-1245 . That fix solves also this issue.

People

  • Assignee:
    Unassigned
    Reporter:
    Jörg Schaible
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: