You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Michael Pilone (JIRA)" <ji...@codehaus.org> on 2010/08/24 13:50:34 UTC

[jira] Issue Comment Edited: (MASSEMBLY-242) transitive dependencies do not get included

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

Michael Pilone edited comment on MASSEMBLY-242 at 8/24/10 6:50 AM:
-------------------------------------------------------------------

I'm still seeing this issue with 2.2 beta 5. As others have described, if I have a dependencySet with explicit includes, the transitive dependencies do not appear to get included.

EDIT: Nevermind, I didn't understand the use of useTransitiveFiltering which was causing all of my transitive dependencies to be filtered out. It is a little counter intuitive that "useTransitiveFiltering" would include more dependencies, but once I understood the dependency trail concept I was able to get things working.

      was (Author: mpilone):
    I'm still seeing this issue with 2.2 beta 5. As others have described, if I have a dependencySet with explicit includes, the transitive dependencies do not appear to get included.
  
> transitive dependencies do not get included
> -------------------------------------------
>
>                 Key: MASSEMBLY-242
>                 URL: http://jira.codehaus.org/browse/MASSEMBLY-242
>             Project: Maven 2.x Assembly Plugin
>          Issue Type: Bug
>    Affects Versions: 2.2-beta-1
>         Environment: maven 2.0.7
>            Reporter: manuel aldana
>            Assignee: John Casey
>             Fix For: 2.2-beta-3
>
>         Attachments: assembly-transitive-dep-failure.zip
>
>
> i am using assembly plugin with standard descriptor jar-with-dependencies. problem is that transitive dependencies do not get included.
> pom.xml from project A:
> ...
>  <groupId>a</groupId>
>  <artifactId>a</artifactId>
>  <version>1.0</version>
>  <dependencies>
>     <dependency>
>       <groupId>tran</groupId>
>       <artifactId>dep</artifactId>
>       <version>1.0</version>
>     </dependency>  
>    </dependencies>
> ...
> pom.xml from project B:
> ...
>  <groupId>b</groupId>
>  <artifactId>b</artifactId>
>  <version>1.0</version>
>  <build>
>      ... enabling assembly-plugin with jar-with-dependencies...
>  </build>
>  <dependencies>
>     <dependency>
>       <groupId>a</groupId>
>       <artifactId>a</artifactId>
>       <version>1.0</version>
>     </dependency>  
>  </dependencies>
> ...
> i am doing assembly:assembly on b:b. now tran:dep does not get included though it is defined in a:a. that means: if i open the assembled jar-file (from b:b) i cannot see any artifacts from tran:dep.
> for earlier discussion on mailingslist see http://www.nabble.com/assembly-plugin%3A-transitive-dependencies-do-not-get-included-tf4317601s177.html#a12308820

-- 
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