Hello, In practise it seems to be a small issue (at least for us). Older branches are seldomly touched and nearly all work with any 3.x versions (the main reason for this is, that we prefer to use Eclipse with its internal default maven). My main pain of switching (mostly JVM) comes from working on OSS projects in parallel to company.
I think it is actually a good idea to keep all active branches somewhat recent. Otherwise you wont get support for those older plugins in case you need it (and you run into these problems). Anyway, I actually have a simple batch file to set my PATH with some usual combinations of java and maven (asf, company6, company7), but the idea of having this information inside the project root directory is attractive for quick switching. I think a promising tool for your need would be jenv. As it is documented now it deals with the java version, but it already brings wrappers for maven, so it might only need a small tweaking to modify the maven path as well. https://github.com/gcuisinier/jenv I somewhat feel this is the better way than letting maven parse the POM and refork itself. Gruss Bernd Am Mon, 2 Feb 2015 08:20:46 -0700 schrieb David Hoffer <[email protected]>: > 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, <[email protected]> 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:[email protected]] > > 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 > > <[email protected]> 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: [email protected] > > > For additional commands, e-mail: [email protected] > > > > > > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
