Ok that's fair. If it ain't broke, don't fix it. Have you tried your builds on newer versions to make sure it would work? There have been some differences between 2.0.5 & 2.0.6 that could require prep work (and you may discover issues you didn't know you had): http://maven.apache.org/plugins/maven-dependency-plugin/examples/prepari ng-dependencies.html
-----Original Message----- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Friday, March 07, 2008 5:48 PM To: Maven Users List Subject: RE: [POLL] Why are you not able to use the most recent maven release? We're currently stuck on 2.0.5 - the problem is getting an entire organization to upgrade. Aside from the, "it works better" response, typically, there needs to be a financial reason explaining why we are asking everyone to stop what they are doing and upgrade. -----Original Message----- From: Brian E. Fox [mailto:[EMAIL PROTECTED] Sent: Friday, March 07, 2008 4:45 PM To: Maven Users List Subject: [POLL] Why are you not able to use the most recent maven release? I get the sense that lots of people are using older versions of Maven due to various regressions. As we get closer to 2.1 alpha, we need to ensure that we identify the regressions across the 2.0 line so that we can make sure they are fixed in 2.1 and so that users can upgrade to a recent 2.0.x before trying out 2.1. If this is the case for you, please reply and state the version you're using and why (preferably referring to a Jira). We will use this information to prioritize issues for 2.0.10 and beyond. Thanks. --------------------------------------------------------------------- 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]
