Details
-
Bug
-
Status: Closed
-
Critical
-
Resolution: Fixed
-
2.0, 2.1, 2.2
-
None
-
None
-
All
-
Patch
Description
The test-jar goal attaches to the project "org.apache.maven.its.it0121:model:jar" such a artifact:
- org.apache.maven.its.it0121:model:jar:tests
It should attach such an artifact: - org.apache.maven.its.it0121:model:test-jar:tests
The wrong artifacts "naming" leads to MNG-2871 problem:
The code does not work (because the strings are different:
-----------------MavenProject: replaceWithActiveArtifact(...)--------------------------------------------
....
Iterator itr = ref.getAttachedArtifacts().iterator();
while(itr.hasNext()) {
Artifact attached = (Artifact) itr.next();
if( attached.getDependencyConflictId().equals(pluginArtifact.getDependencyConflictId()) )
...
-------------------------------------------------------------------------------------------------------------------------------------------
pluginArtifact.getDependencyConflictId() is : org.apache.maven.its.it0121:model:test-jar:tests
attached.getDependencyConflictId() is : org.apache.maven.its.it0121:model:jar:tests
For test-case: look at test (it121) attached to: http://jira.codehaus.org/browse/MNG-2871
Attachments
Attachments
Issue Links
- is depended upon by
-
MNG-2045 Maven can't compile against sibling test-jar dependency in multiproject (Test Attached)
- Closed
-
MNG-2871 Subartifact (ejb-client, test-jar etc.) are not reselved as active project artifacts in build phases prior to package
- Closed
-
MNG-3043 Allow 'mvn test' to work with test-jar dependencies in a reactor
- Closed
-
MNG-3076 Dependency on test-jar is not resolved with 'package' target, must use 'install'
- Closed
-
MNG-4248 CLONE -Maven can't compile against sibling test-jar dependency in multiproject (Test Attached)
- Closed
-
MRELEASE-285 Unresolved test-jar dependency during release
- Closed