maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kurt T Stam (JIRA)" <>
Subject [jira] (MSOURCES-66) source and javadoc jars from test-jar not added to assembly
Date Tue, 04 Jun 2013 13:01:03 GMT
Kurt T Stam created MSOURCES-66:

             Summary: source and javadoc jars from test-jar not added to assembly
                 Key: MSOURCES-66
             Project: Maven 2.x Source Plugin
          Issue Type: Bug
    Affects Versions: 2.2
            Reporter: Kurt T Stam

I'm trying to add 'test-jar' resources to my assembly; i.e. the following jars are created
by one of our other modules:

-rw-r--r--   1 kstam  admin     11603 Jun  3 11:29 uddi-tck-3.2.0-SNAPSHOT.jar
-rw-r--r--   1 kstam  admin     27880 Jun  3 11:29 uddi-tck-3.2.0-SNAPSHOT-javadoc.jar
-rw-r--r--   1 kstam  admin      8873 Jun  3 11:29 uddi-tck-3.2.0-SNAPSHOT-sources.jar
-rw-r--r--   1 kstam  admin    106397 Jun  3 11:29 uddi-tck-3.2.0-SNAPSHOT-tests.jar
-rw-r--r--   1 kstam  admin    149558 Jun  3 11:29 uddi-tck-3.2.0-SNAPSHOT-test-javadoc.jar
-rw-r--r--   1 kstam  admin     62545 Jun  3 11:29 uddi-tck-3.2.0-SNAPSHOT-test-sources.jar

I can successfully add the uddi-tck-3.2.0-SNAPSHOT-tests.jar to my assembly using



However when I try to add the source jar:
        <!-- The source archives JARs -->

Then the uddi-tck-3.2.0-SNAPSHOT-sources.jar is NOT picked up. I made sure we reference the
and javadoc artifacts in the pom.xml:


Full pom and assembly.xml:

When running with -X it says:

[DEBUG] Adding artifact: org.apache.juddi:uddi-tck:test-jar:sources:3.2.0-SNAPSHOT with file:
to assembly location: src/uddi-tck-3.2.0-SNAPSHOT-sources.jar.

so it seem to be adding the source *jar*, rather then the *test-jar*. eventhough it says it's
going to add the *test-jar* version:

Adding artifact: org.apache.juddi:uddi-tck:test-jar:sources:3.2.0-SNAPSHOT 

To reproduce check out

cd uddi-client-dist
mvn package -DskipTests=true

Note that the javadoc plugin seems to have the same issue. 



This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message