[MNG-3076] Dependency on test-jar is not resolved with 'package' target, must use 'install'

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 2.0.7
• Assignee: Unassigned
• Reporter: Dainius Vaznys
• Created: 29/Jun/07 04:20
• Updated: 06/Apr/15 00:05
• Resolved: 29/Oct/07 18:10

Description

The multi-module project looks like this:
/ipb – this is where the build is run from
/ipb-base – this guy builds a test jar, ipb-base-1.0-SNAPSHOT-tests.jar
/ipb-something, it has some tests that use ipb-base-1.0-SNAPSHOT-tests.jar so its dependency looks like this:

<!-- regular stuff from base project -->
<dependency>
<groupId>com.exigen.ipb</groupId>
<artifactId>ipb-base</artifactId>
</dependency>
<!-- stuff for unit tests from base project -->
<dependency>
<groupId>com.exigen.ipb</groupId>
<artifactId>ipb-base</artifactId>
<type>test-jar</type>
<scope>test</scope>
</dependency>

Both /ipb-base and /ipb-something are packaged as jars.

Now when the build is run as 'mvn clean package' it cannot resolve the dependecy as it is not in the repo.

Runing build as 'mvn clean install' does the trick however this seems to be a workaround – one would expect 'clean package' to do the job.

Issue Links

• depends upon: MJAR-75 [PATCH] Wrong artifact type attached to the project by the test-jar goal
• depends upon: MNG-2877 unable to resolve attached artifacts from reactor that are not in repo. (patch applied in svn and IT tests added)
• duplicates: MNG-3043 Allow 'mvn test' to work with test-jar dependencies in a reactor