Hi Karl, Our posts crossed. We use several different Maven versions but upgrading has always been problematic because it's hard if not impossible to upgrade all projects to the latest. It's easy to upgrade the trunk (usually) but we have older branches where we do not want to upgrade because we want minimal changes in that branch build (e.g. no plugin changes).
We can't use Jenkins...but that's not an issue...as for CI we have no problem running the version we want. The issue is for developers...I don't want devs to have to constantly switch their environment around just to run different maven versions. We often have to run both at the same time as we are fixing something in a branch and the same in trunk after the merge. This is a standard feature of Gradle and lots of folks here are pushing for that. If Maven had this feature it would remove their argument. -Dave On Mon, Feb 2, 2015 at 8:20 AM, David Hoffer <dhoff...@gmail.com> wrote: > That's great that Jenkins does this but we need it built into Maven > directly. Our CI infrastructure is TeamCity with many hundreds of builds > and that's not going to change any time soon and we need developers to get > the same feature from the command line & integrated with their IDE. > > -Dave > > On Mon, Feb 2, 2015 at 8:12 AM, <cody.a.fy...@wellsfargo.com> wrote: > >> I have to admit, this would be pretty cool. >> >> However, Jenkins already has this functionality. You specify the Maven >> version in the job and configure Jenkins to automatically download that >> version (it does with this with Java and Ant as well). >> >> I highly suggest you look into it. Even running it on your local machine >> is pretty convenient. >> >> Cody Fyler >> Lending Grid Build Team >> G=Lending Grid Builds >> (515) – 441 - 0814 >> >> -----Original Message----- >> From: David Hoffer [mailto:dhoff...@gmail.com] >> Sent: Monday, February 02, 2015 9:06 AM >> To: Maven Users List >> Subject: Re: maven 3.0.6 release date >> >> On a somewhat related note, one feature I'd like to see added to Maven is >> the ability to easily upgrade the version of Maven used. I want the build >> to specify the version of Maven used and automatically download and use >> that version. Currently it's the system that determines what version is >> installed on the path. The best a project can do is require a (min) >> version of Maven. This makes it hard to upgrade as we have several >> projects to support and some will never be upgraded as they are older >> branches. Is this feature on the Maven radar? >> >> On Mon, Feb 2, 2015 at 6:27 AM, Karl Heinz Marbaise <khmarba...@gmx.de> >> wrote: >> >> > Hi, >> > >> > isn't it an option to update to 3.2.5 ? Have you tried it ? >> > >> > >> > On 2/2/15 10:27 AM, Bichov, Vitaly wrote: >> > >> >> Hi, >> >> >> >> There is this (http://jira.codehaus.org/browse/MNG-5315) bug. >> >> The bug has a fix proposal and a workaround. >> >> Due to some restrictions I can't apply the workaround on my >> environment. >> >> >> >> Will the bug be fixed in the next (3.0.6) release? >> >> When will 3.0.6 version will be released if ever? >> >> >> >> Thank you, >> >> Vitaly >> >> >> >> >> > Kind regards >> > Karl Heinz Marbaise >> > >> > --------------------------------------------------------------------- >> > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org >> > For additional commands, e-mail: users-h...@maven.apache.org >> > >> > >> > >
