You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Peter Jones (JIRA)" <ji...@apache.org> on 2007/02/07 01:23:05 UTC
[jira] Created: (CXF-410) specifying exclusions tag in pom.xml can
cause issues with ibm jdk
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.
[jira] Commented: (CXF-410) specifying exclusions tag in pom.xml
can cause issues with ibm jdk
Posted by "Peter Jones (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12471073 ]
Peter Jones commented on CXF-410:
---------------------------------
Thanks for the suggestion! I just wiped junit from my local repository and tried running again. However, still see the problem that when the <exclusion> block isn't commented out, junit doesn't get added to the test compile stage of the build. :(
> 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.
[jira] Commented: (CXF-410) specifying exclusions tag in pom.xml
can cause issues with ibm jdk
Posted by "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.
[jira] Commented: (CXF-410) specifying exclusions tag in pom.xml
can cause issues with ibm jdk
Posted by "Daniel Kulp (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12471081 ]
Daniel Kulp commented on CXF-410:
---------------------------------
I actually believe this is a bug in Maven 2.0.4 that is/will be fixed in Maven 2.0.5. Unfortunately, the release candidate I was using has been removed from Jason's home directory on p.a.o. Hopefully a new one will appear soon that you can test out. Alternatively, you could checkout the maven_2.0.x branch (https://svn.apache.org/repos/asf/maven/components/branches/maven-2.0.x) and build it and try it. If 2.0.5 fixes it, that would be great.
> 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.
[jira] Closed: (CXF-410) specifying exclusions tag in pom.xml can
cause issues with ibm jdk
Posted by "Peter Jones (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Peter Jones closed CXF-410.
---------------------------
Resolution: Fixed
> 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.
[jira] Commented: (CXF-410) specifying exclusions tag in pom.xml
can cause issues with ibm jdk
Posted by "Peter Jones (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12472175 ]
Peter Jones commented on CXF-410:
---------------------------------
Thanks Dan. Just tried the latest from the maven-2.0.x branch - 2.0.6-SNAPSHOT and the bug is fixed with this version of mvn. So it'll be necessary to use a version of maven > 2.0.4 to work with the ibm jdk.
> 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.