[MDEP-106] Unpacking primary artifact from sibling module uses repository rather than reactor

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 2.0-alpha-4
• Component/s: unpack
• Assignee: Brian E Fox
• Reporter: Matt Ryall
• Created: 29/Aug/07 02:53
• Updated: 10/Mar/16 13:50
• Resolved: 14/Jul/11 02:44

Description

Running dependency:unpack referencing a project in the reactor has the following output which shows it is scanning for repository artifacts rather than the artifact in the reactor:

[INFO] [dependency:unpack \{execution: unpack-tests}]
[INFO] Configured Artifact: com.example.app:app-acceptance-test:2.6-SNAPSHOT:jar
[INFO] snapshot com.example.app:app-acceptance-test:2.6-SNAPSHOT: checking for updates from snapshots
[INFO] snapshot com.example.app:app-acceptance-test:2.6-SNAPSHOT: checking for updates from m1-repo
Downloading: http://m2proxy:8081/artifactory/repo/com/example/app/app-acceptance-test/2.6-SNAPSHOT/app-acceptance-test-2.6-20070829.025709-409.jar
9125K downloaded
[INFO] Expanding: /Users/mryall/.m2/repository/com/example/app/app-acceptance-test/2.6-SNAPSHOT/app-acceptance-test-2.6-SNAPSHOT.jar into /Users/mryall/src/example/app/app-webapp/target/it-classes

To explain the scenario: to build reusable acceptance tests, I have the following sub-modules of my project:

• app-core (jar)
• app-acceptance-tests (jar)
• app-webapp (war)

The acceptance tests are packaged this way for further use in testing, and also run against the webapp in the integration-test phase. This is where the problem arises.

Running 'mvn clean integration-test' does the following relevant tasks:

• in the app-acceptance-test module, compiles and packages a JAR of tests
• in the app-webapp module, uses the dependency:unpack goal to extract the tests into target/it-classes in the pre-integration-test phase, and test:test to run them in the integration test phase.

I don't think this is caused by the snapshot version, because the release plugin also fails because it is unable to find the 2.6 version when it runs 'mvn clean verify'. There, it scans all the repositories for the acceptance test artifact before failing with the usual error:

[INFO] Failed to resolve artifact.

GroupId: com.example.app
ArtifactId: app-acceptance-test
Version: 2.6

Reason: Unable to download the artifact from any repository

Maven details:

$ mvn -version
Maven version: 2.0.7
Java version: 1.4.2_12
OS name: "mac os x" version: "10.4.10" arch: "i386"

Issue Links

• duplicates: MDEP-316 dependency:copy and dependency:unpack behave differently with M2 and M3 (should always search the reactor for artifacts)
• is related to: MDEP-44 unpacking/copying of attached artifacts from reactor projects doesn't work
• relates to: MDEP-153 Active dependencies being unpacked but not listed as normal dependencies are not used by the reactor in determing build order