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] > >
