You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Martin Ritchie (JIRA)" <qp...@incubator.apache.org> on 2007/02/08 15:45:05 UTC

[jira] Resolved: (QPID-297) Maven build broken by exclusions on JUnit

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