> Considering the following page if you have to edit some plugins, it could be > nice to try to upgrade (if possible) some > dependencies.
Yeah, I say we make a rule that you can't release a plugin now without upgrading the dependencies to the highest common denominator, unless there is a reason not to (eg ant) :) > > http://maven.apache.org/reference/plugins/dependency-convergence-report.html > None of these are really problematic - apart from ant, they are quite small downloads I think. > For example there are several plugins that use a dependency to an old maven > core release > http://maven.apache.org/reference/plugins/dependency-convergence-report.html#maven:maven > Can't it create some classloader problems ?? No. All those plugins actually reference ${maven.home}/lib/maven.jar now and never download the old version. Removing the <version> tag would be a good idea if it worked. > There was also a problem on the xdoc plugin (a problem with entities) that > was fixed upgrading the jelly-tags Yep, and this version is now bundled in maven, so we could actually remove the xml tags from all the plugins if desired. - Brett --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
