You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Joshua Pollak (JIRA)" <ji...@codehaus.org> on 2008/12/03 17:04:19 UTC

[jira] Commented: (MASSEMBLY-368) In a DependencySet I cannot get scope to be transitive

    [ http://jira.codehaus.org/browse/MASSEMBLY-368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=156548#action_156548 ] 

Joshua Pollak commented on MASSEMBLY-368:
-----------------------------------------

I have the same problem with the tar.gz format. This is the head of my assembly xml file:

{{monospaced}}
<assembly>
    <id>plugin</id>
    <formats>
        <format>tar.gz</format>
    </formats>
    <baseDirectory>${project.artifactId}-${project.version}</baseDirectory>
    <dependencySets>
        <dependencySet>
            <outputDirectory>lib</outputDirectory>
            <useTransitiveDependencies>true</useTransitiveDependencies>
            <useTransitiveFiltering>false</useTransitiveFiltering>
            <includes>
                <include>org.mule.transports:mule-transport-sqs</include>
            </includes>
        </dependencySet>
     </dependencySets>
...
{{monospaced}}

The mule-transport-sqs depends on a library called typica, which depends on a few other libraries. The only jar to appear in the lib directory is the mhs-transport-sqs itself.

I added <useTransitiveFiltering>false</useTransitiveFiltering> in an effort to fix the problem (I know false is the default), but it didn't help.

> In a DependencySet I cannot get scope to be transitive
> ------------------------------------------------------
>
>                 Key: MASSEMBLY-368
>                 URL: http://jira.codehaus.org/browse/MASSEMBLY-368
>             Project: Maven 2.x Assembly Plugin
>          Issue Type: Bug
>    Affects Versions: 2.2-beta-2
>         Environment: I define an assembly having the  "dir" format.
>            Reporter: Jean-Sébastien Scrève
>
> I have a project "A" who has a dependency to another project named "myDomain".
> <dependency>
> 	<groupId>myDomain</groupId>
> 	<artifactId>myDomain</artifactId>
> 	<version>1.0.0</version>
> 	<scope>provided</scope>
> </dependency>
> myDomain also has others "provided" dependencies :
> <dependency>
> 	<groupId>asm</groupId>
> 	<artifactId>asm</artifactId>
> 	<version>2.2.3</version>
> 	<scope>provided</scope>
> </dependency>
> <dependency>
> 	<groupId>asm</groupId>
> 	<artifactId>asm-attrs</artifactId>
> 	<version>2.2.3</version>
> 	<scope>provided</scope>
> </dependency>
> In my assembly descriptor, I define the following dependency set :
> <dependencySet>
> 	<useProjectArtifact>false</useProjectArtifact>
> 	<useTransitiveDependencies>true</useTransitiveDependencies>
> 	<outputDirectory></outputDirectory>
> 	<unpack>false</unpack>
> 	<scope>provided</scope>
> </dependencySet>
> None of the "provided" dependencies of myDomain project are included into my assembly. 
> That is :asm:asm and asm:asm-attrs are not included but myDomain:myDomain is included.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira