commons-collections version is 2.1.1 when root.pom depends on 3.2 ----------------------------------------------------------------- Key: JBSEAM-2603 URL: http://jira.jboss.com/jira/browse/JBSEAM-2603 Project: JBoss Seam Issue Type: Bug Components: Build Affects Versions: 2.1.0.GA Reporter: Jay Balunas Something in the wicket build is downloading an older version of commons-collections 2.1.1, while in the Seam_2_0 branch it is using 3.2. I has searched through the poms, but I think that it is one of child dependencies of wicket's dependencies. Our root.pom.xml file states a dependency on commons-collections-3.2. The symptom I'm seeing is when attempting to deploy to websphere I am getting ClassNoFoundExceptions. Not sure if it effects other deployments. Below is the snippet from the build where it is downloading 2.1.1 during wicket build after I deleted original from repository. initwicket: [echo] Build JBoss Seam wicket 2.1 [mkdir] Created dir: /rhdev/projects/jboss-seam/svn-head/jboss-seam-svn/classes/wicketclasses [copy] Copying 1 file to /rhdev/projects/jboss-seam/svn-head/jboss-seam-svn/classes/wicketclasses [artifact:dependencies] Downloading: commons-collections/commons-collections/2.1.1/commons-collections-2.1.1.pom from repository.jboss.org [artifact:dependencies] Transferring 0K from repository.jboss.org [artifact:dependencies] Downloading: commons-collections/commons-collections/2.1.1/commons-collections-2.1.1.jar from repository.jboss.org [artifact:dependencies] Transferring 171K from repository.jboss.org [artifact:dependencies] [WARNING] *** CHECKSUM FAILED - Error retrieving checksum file for commons-collections/commons-collections/2.1.1/commons-collections-2.1.1.jar - IGNORING compilewicket: [javac] Compiling 20 source files to /rhdev/projects/jboss-seam/svn-head/jboss-seam-svn/classes/wicketclasses [javac] Note: Some input files use unchecked or unsafe operations. [javac] Note: Recompile with -Xlint:unchecked for details. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira