[ 
https://jira.codehaus.org/browse/MSOURCES-66?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Stephen Connolly closed MSOURCES-66.
------------------------------------

    Resolution: Not A Bug

The artifacts are all of type "jar" with classifiers "test-sources" and 
"test-javadoc" respectively.

{code}
<include>org.apache.juddi:uddi-tck:jar:test-sources</include>
<include>org.apache.juddi:uddi-tck:jar:test-javadoc</include>
{code}

Not a bug, rather a side-effect of the convenience packaging type "test-jar" 
which caused confusion on your behalf
                
> source and javadoc jars from test-jar not added to assembly
> -----------------------------------------------------------
>
>                 Key: MSOURCES-66
>                 URL: https://jira.codehaus.org/browse/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:
> main:
> -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
> test:
> -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
>  ...
> <dependencySet>
> <outputDirectory>bin</outputDirectory>
>             <includes>
> <include>org.apache.juddi:juddi-client:jar</include>
> <include>org.apache.juddi:uddi-tck:jar</include>
> <include>org.apache.juddi:uddi-tck:test-jar</include>
> ...
> However when I try to add the source jar:
> ...
>         <!-- The source archives JARs -->
>         <dependencySet>
> <outputDirectory>src</outputDirectory>
>             <scope>test</scope>
>             <includes>
> <include>org.apache.juddi:juddi-client:jar:sources</include>
> <include>org.apache.juddi:uddi-tck:jar:sources</include>
> <include>org.apache.juddi:uddi-tck:test-jar:sources</include>
> ...
> Then the uddi-tck-3.2.0-SNAPSHOT-sources.jar is NOT picked up. I made sure we 
> reference the source
> and javadoc artifacts in the pom.xml:
>       <dependency>
>             <groupId>org.apache.juddi</groupId>
>             <artifactId>uddi-tck</artifactId>
> <version>${project.parent.version}</version>
>             <type>test-jar</type>
>             <classifier>sources</classifier>
>         </dependency>
>    <dependency>
>             <groupId>org.apache.juddi</groupId>
>             <artifactId>uddi-tck</artifactId>
> <version>${project.parent.version}</version>
>             <classifier>javadoc</classifier>
>             <type>test-jar</type>
>         </dependency>
> Full pom and assembly.xml:
> http://svn.apache.org/repos/asf/juddi/trunk/uddi-client-dist/pom.xml
> http://svn.apache.org/repos/asf/juddi/trunk/uddi-client-dist/src/main/assembly/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: 
> /Users/kstam/.m2/repository/org/apache/juddi/uddi-tck/3.2.0-SNAPSHOT/uddi-tck-3.2.0-SNAPSHOT-sources.jar
>  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 http://svn.apache.org/repos/asf/juddi/trunk/
> cd uddi-client-dist
> mvn package -DskipTests=true
> Note that the javadoc plugin seems to have the same issue. 
> Cheers,
> --Kurt

--
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: http://www.atlassian.com/software/jira

Reply via email to