You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Rupert Smith (JIRA)" <qp...@incubator.apache.org> on 2007/01/15 17:57:27 UTC
[jira] Created: (QPID-297) Maven build broken by exclusions on
JUnit
Maven build broken by exclusions on JUnit
-----------------------------------------
Key: QPID-297
URL: https://issues.apache.org/jira/browse/QPID-297
Project: Qpid
Issue Type: Bug
Components: Maven build system
Reporter: Rupert Smith
This seems to be due to the exclusion of junit (3.7.1) as an incorrect depency of commons-lang:
<dependency>
<groupId>commons-lang</groupId>
<artifactId>commons-lang</artifactId>
<version>2.1</version>
<exclusions>
<exclusion>
<groupId>junit</groupId>
<artifactId>junit</artifactId>
</exclusion>
</exclusions>
</dependency>
Accoring to the article below, the exclusion from common-lang should not affect anything else. So the seperate declaration for junit 3.8.1 should not be wiped out by this. Removing the exclusion gets my build working though.
http://maven.apache.org/guides/introduction/introduction-to-optional-and-excludes-dependencies.html
Looks like a maven bug, can I suggest putting exclusions in the assembly descriptors instead?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (QPID-297) Maven build broken by exclusions on
JUnit
Posted by "Martin Ritchie (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Ritchie resolved QPID-297.
---------------------------------
Resolution: Fixed
> Maven build broken by exclusions on JUnit
> -----------------------------------------
>
> Key: QPID-297
> URL: https://issues.apache.org/jira/browse/QPID-297
> Project: Qpid
> Issue Type: Bug
> Components: Maven build system
> Reporter: Rupert Smith
> Attachments: Qpid-297.diff
>
>
> This seems to be due to the exclusion of junit (3.7.1) as an incorrect depency of commons-lang:
> <dependency>
> <groupId>commons-lang</groupId>
> <artifactId>commons-lang</artifactId>
> <version>2.1</version>
> <exclusions>
> <exclusion>
> <groupId>junit</groupId>
> <artifactId>junit</artifactId>
> </exclusion>
> </exclusions>
> </dependency>
> Accoring to the article below, the exclusion from common-lang should not affect anything else. So the seperate declaration for junit 3.8.1 should not be wiped out by this. Removing the exclusion gets my build working though.
> http://maven.apache.org/guides/introduction/introduction-to-optional-and-excludes-dependencies.html
> Looks like a maven bug, can I suggest putting exclusions in the assembly descriptors instead?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (QPID-297) Maven build broken by exclusions on
JUnit
Posted by "Rupert Smith (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rupert Smith updated QPID-297:
------------------------------
Attachment: Qpid-297.diff
> Maven build broken by exclusions on JUnit
> -----------------------------------------
>
> Key: QPID-297
> URL: https://issues.apache.org/jira/browse/QPID-297
> Project: Qpid
> Issue Type: Bug
> Components: Maven build system
> Reporter: Rupert Smith
> Attachments: Qpid-297.diff
>
>
> This seems to be due to the exclusion of junit (3.7.1) as an incorrect depency of commons-lang:
> <dependency>
> <groupId>commons-lang</groupId>
> <artifactId>commons-lang</artifactId>
> <version>2.1</version>
> <exclusions>
> <exclusion>
> <groupId>junit</groupId>
> <artifactId>junit</artifactId>
> </exclusion>
> </exclusions>
> </dependency>
> Accoring to the article below, the exclusion from common-lang should not affect anything else. So the seperate declaration for junit 3.8.1 should not be wiped out by this. Removing the exclusion gets my build working though.
> http://maven.apache.org/guides/introduction/introduction-to-optional-and-excludes-dependencies.html
> Looks like a maven bug, can I suggest putting exclusions in the assembly descriptors instead?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira