[jira] Commented: (CXF-410) specifying exclusions tag in pom.xml can cause issues with ibm jdk

["Gary Tully (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CXF-410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12470845 ] 

Gary Tully commented on CXF-410:
--------------------------------

Hi, i tracked down a similar issue to the exclusion in the pom only to find that the problem related to my maven repository in some way. I did not manage to resolve the root cause but the problem related to different versions of junit being pulled in by different components. When i selectivly refreshed the referenced components (deleted them from my .m2/...) the problem disappeared. Well, i think the referenced versions of junit sorted them selves out. mvn -X helped show what was going on. Possibly your issue is similar?

> specifying exclusions tag in pom.xml can cause issues with ibm jdk
> ------------------------------------------------------------------
>
>                 Key: CXF-410
>                 URL: https://issues.apache.org/jira/browse/CXF-410
>             Project: CXF
>          Issue Type: Sub-task
>            Reporter: Peter Jones
>         Assigned To: Peter Jones
>
> For instance,  bindings/http/pom.xml has something like this:
>     <dependencies>
>         <dependency>
>             <groupId>org.codehaus.jra</groupId>
>             <artifactId>jra</artifactId>
>             <version>1.0-alpha-1</version>
>             <exclusions>
>                 <exclusion>
>                     <groupId>junit</groupId>
>                     <artifactId>junit</artifactId>
>                 </exclusion>
>             </exclusions>
>         </dependency>
>         <dependency>
>             <groupId>junit</groupId>
>             <artifactId>junit</artifactId>
>             <scope>test</scope>
>         </dependency>
> The exclusion of junit from jra - which I believe is meant to prevent junit from being packaged - causes the second junit dependency to be removed with the ibm jdk.  So the tests won't compile.  The workaround is to comment out the exclusion from the pom.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.