[ http://jira.codehaus.org/browse/MEV-293?page=comments#action_56227 ]
fabrizio giustina commented on MEV-293: --------------------------------------- Actually in a big multiproject build the amount of warnings produced by relocated jars is really annoying (lots of common dependencies have been relocated like xml apis, servletapi, etc.) A good build should be able to complete *without* warnings... relocation warnings hide other important warning and messages the user should consider. IMHO we should choose one of the following: - or we fix relocated dependencies in POMS already in the repository (manually or by writing a tool which scans the repo and rewrite POM dependencies periodically till everything will be fixed) - or we shut up maven by making it reporting only DIRECT relocated dependencies and ignoring transitive one (so you know if you have to fix your pom but you are not warned if someone else has a "bad" pom you can't fix in any way) > Fix xml-apis dependency in commons-pool poms > -------------------------------------------- > > Key: MEV-293 > URL: http://jira.codehaus.org/browse/MEV-293 > Project: Maven Evangelism > Type: Task > Components: Dependencies > Reporter: fabrizio giustina > Assignee: Carlos Sanchez > > > pom contains a dependency on xml-apis:2.0.2, which has been relocated to > xml-apis:1.0.b2. > Should be fixed with: > <dependency> > <groupId>xml-apis</groupId> > <artifactId>xml-apis</artifactId> > <version>1.0.b2</version> > </dependency> > Same issue also for other commons-pool versions -- 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]
