I'm sort of in the same boat, but for different reasons. The maven version is considered to be part of the configuration for each project, so projects are tied to whatever version of Maven was used at release time. Upgrades are considered to be changes to the build environment, which are out of scope in certain projects (small patch releases, for example). We play it safe in these cases because changes to Maven versions can cause build-related regressions.
We also use Continuum as our CI environment, and Continuum is tied to whatever Maven version the Continuum unix account uses, which means that we are forced to use the same Maven version for all projects in Continuum. Upgrading the maven that Continuum uses forces all projects to upgrade Maven versions. Until I can figure out a way to get Continuum to run with different Maven versions, we're stuck with the current one. Either that, or I get the entire development team to upgrade simultaneously to a new Maven version. (Which might not really be such a big deal, IMO.) We're currently stuck on 2.0.4 but are starting to plan to upgrade to 2.0.9. 2.1 is not even on the radar yet. Ken On 3/7/08, EJ Ciramella <[EMAIL PROTECTED]> wrote: > > 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] > >
