maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Frank Wilson (JIRA)" <j...@codehaus.org>
Subject [jira] (MASSEMBLY-675) Maven Assembly packaging excluded dependencies
Date Mon, 02 Dec 2013 17:42:45 GMT

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

Frank Wilson updated MASSEMBLY-675:
-----------------------------------

    Environment: 
Apache Maven 3.1.1
Java version: 1.7.0_45, vendor: Oracle Corporation
OS name: "mac os x", version: "10.8.4", arch: "x86_64", family: "mac"

  was:
Apache Maven 3.1.1 (0728685237757ffbf44136acec0402957f723d9a; 2013-09-17 16:22:22+0100)
Java version: 1.7.0_45, vendor: Oracle Corporation
OS name: "mac os x", version: "10.8.4", arch: "x86_64", family: "mac"

    
> Maven Assembly packaging excluded dependencies
> ----------------------------------------------
>
>                 Key: MASSEMBLY-675
>                 URL: https://jira.codehaus.org/browse/MASSEMBLY-675
>             Project: Maven Assembly Plugin
>          Issue Type: Bug
>    Affects Versions: 2.4
>         Environment: Apache Maven 3.1.1
> Java version: 1.7.0_45, vendor: Oracle Corporation
> OS name: "mac os x", version: "10.8.4", arch: "x86_64", family: "mac"
>            Reporter: Frank Wilson
>            Assignee: John Casey
>
> 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, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message