Agreed. If it ain't broke, don't fix it. On Fri, Jun 18, 2010 at 10:22 AM, Niall Pemberton <[email protected]> wrote: > On Fri, Jun 18, 2010 at 11:11 AM, sebb <[email protected]> wrote: >> If we are updating parent to fix the deployment URLs, we should >> probably update plugin versions too. >> >> The following plugin updates are available: >> org.apache.felix:maven-bundle-plugin ................. 1.4.3 -> 2.1.0 >> maven-antrun-plugin ...................................... 1.3 -> 1.4 >> maven-clean-plugin ..................................... 2.4 -> 2.4.1 >> maven-compiler-plugin .................................. 2.1 -> 2.3.1 >> maven-gpg-plugin ......................................... 1.0 -> 1.1 >> maven-install-plugin ................................... 2.3 -> 2.3.1 >> maven-jar-plugin ....................................... 2.3 -> 2.3.1 >> maven-javadoc-plugin ..................................... 2.5 -> 2.7 >> maven-jxr-plugin ......................................... 2.1 -> 2.2 >> maven-project-info-reports-plugin ...................... 2.1.2 -> 2.2 >> maven-remote-resources-plugin ............................ 1.0 -> 1.1 >> maven-resources-plugin ............................... 2.4.1 -> 2.4.3 >> maven-site-plugin .................................... 2.0.1 -> 2.1.1 >> maven-source-plugin .................................. 2.1.1 -> 2.1.2 >> >> gpg 1.1 is definitely worthwhile, particularly if using GPG2. >> >> antrun 1.4 should NOT be used (see >> http://jira.codehaus.org/browse/MANTRUN-143) >> >> I think most of the rest are probably OK - any thoughts? >> >> Some of the above will probably require at least Maven 2.1.0 and/or >> Java 1.5, but now that we have enabled the java profiles, IMO these >> are not issues any more. > > When I did the last commons-parent release doing these mass upgrades > caused problems with some components. I would say we should only do > this if there is time to test for each component. Otherwise only > upgrade plugins that we know resolve an existing issue. > > Niall > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
--------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
