You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "John Casey (JIRA)" <ji...@codehaus.org> on 2010/09/23 16:14:32 UTC

[jira] Commented: (MASSEMBLY-444) Maven Assembly trying to package excluded dependencies

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

John Casey commented on MASSEMBLY-444:
--------------------------------------

Are you sure there isn't another dependency bringing in these dependencies? Do you have a test project that displays the error?

> Maven Assembly trying to package excluded dependencies
> ------------------------------------------------------
>
>                 Key: MASSEMBLY-444
>                 URL: http://jira.codehaus.org/browse/MASSEMBLY-444
>             Project: Maven 2.x Assembly Plugin
>          Issue Type: Bug
>    Affects Versions: 2.2-beta-4
>         Environment: Eclipse, m2eclipse
>            Reporter: Keith Barlow
>
> The maven assembly does not seem to be ignoring dependencies that have been listed in the exclude section of the pom.  This seems to be the same as http://jira.codehaus.org/browse/MASSEMBLY-236 which appears to have been closed without resolution:
> Example:
> I have tried versions 2.2-beta-3, and beta-4 and this still appears to be an issue... is there any idea when this might be addressed?
> It looks like there is some confusion above so I thought this might clarify. When a pom declares a dependency such as log4j which has dependencies that are not in the maven repository, one can add them to the exclusion listing... however the maven-assembly-plugin does not seem to be ignoring them as it should when running a the jar-with-dependencies task and the build fails:
> <dependency>
> <groupId>log4j</groupId>
> <artifactId>log4j</artifactId>
> <version>1.2.15</version>
> <exclusions>
> <exclusion>
> <artifactId>jms</artifactId>
> <groupId>javax.jms</groupId>
> </exclusion>
> <exclusion>
> <artifactId>jmxtools</artifactId>
> <groupId>com.sun.jdmk</groupId>
> </exclusion>
> <exclusion>
> <artifactId>jmxri</artifactId>
> <groupId>com.sun.jmx</groupId>
> </exclusion>
> </exclusions>
> </dependency>

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