[
http://jira.codehaus.org/browse/MASSEMBLY-236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=188980#action_188980
]
Keith Barlow commented on MASSEMBLY-236:
----------------------------------------
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>
Thanks.
Keith
> assembly:assembly resolves excluded artifacts
> ---------------------------------------------
>
> Key: MASSEMBLY-236
> URL: http://jira.codehaus.org/browse/MASSEMBLY-236
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
> Reporter: Daniel Siegmann
> Assignee: John Casey
> Priority: Minor
> Fix For: 2.2-beta-3
>
>
> When creating an assembly, excluded dependencies are still resolved. If the
> artifact can't be resolved, the assembly fails, even though this artifact
> should be excluded.
> This behavior can be seen in the test project attached to issue MASSEMBLY-235.
--
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
