Affects Version/s: None
Fix Version/s: None
Environment:Linux (Ubuntu 8.10), i386, java version "1.6.0_10", Java(TM) SE Runtime Environment (build 1.6.0_10-b33), Java HotSpot(TM) Server VM (build 11.0-b15, mixed mode), Maven 2.0.9
After strugling with xerces 1.4.0 sneaking onto my classpath whenever I ran mvn eclipse:eclipse I was asked to submit the minimal pom which recreates the problem.
The dependency in my original project which caused the problem is an artifact developed by us, which has a dependency to Castor 1.1.1. Castor has a direct dependency to xerces 1.4.0 which is visible when running dependency:tree on the ijcommons-distribution project (which is our local artifact). The problem arises when we run dependency:tree on the initial project, which has a dependency to ijcommons-distribution - then the dependency to castor and xerces is never shown, even if xerces is included on the classpath.
Attached is the 3 poms I used to produce the problem.
"mvn dependency:tree | grep xerces" on the project using "original-problem-pom.xml", gives the following output:
"mvn dependency:tree" on the project using "ijcommons-distribution-pom.xml", gives the following output:
By adding every single dependency of original-problem-pom.xml to minimal-reproduce-pom.xml I confirmed that ijcommons-distribution.xml was the only dependency adding xerces 1.4.0 to the classpath.
To my understanding xerces-1.4.0 should then also appear on the classpath of the project using original-problem-pom.xml?
The POM of Castor version 1.1.1 is also attached.