[ http://jira.codehaus.org/browse/MEV-265?page=comments#action_53698 ]
Matt Raible commented on MEV-265: --------------------------------- This same issue happens with commons-dbcp-1.2.1 and commons-pool-1.2. Correcting the version number in each of these library's POMs fixes the problem. However, I can't help but think that's there some logic messed up somewhere. How does a version 2.0.2 get relocated to a 1.0.b2? That seems quite strange to me. Matt > Commons Digester has invalid version number specified for xml-apis > ------------------------------------------------------------------ > > Key: MEV-265 > URL: http://jira.codehaus.org/browse/MEV-265 > Project: Maven Evangelism > Type: Bug > Components: Invalid POM > Reporter: Matt Raible > > > My project has a transitive dependency on commons-digester 1.5 (via > springmodules/springmodules-validator). I get the following warning when > running my build process. > [artifact:dependencies] [WARNING] While downloading xml-apis:xml-apis:2.0.2 > [artifact:dependencies] This artifact has been relocated to > xml-apis:xml-apis:1.0.b2. > If I modify > ~/.m2/repository/commons-digester/commons-digester/1.5/commons-digester-1.5.pom > and change xml-apis' version from 2.0.2 to 1.0.b2, the warning goes away. > Please change commons-digester-1.5.pom to use 1.0.b2 for xml-apis' version > instead of 2.0.2. > Also, since I've never had the need to include xml-apis.jar in my WAR > projects, it seems that this dependency's scope should be set to "provided". -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
