Hi David,
On 2/2/15 4:05 PM, David Hoffer wrote:
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.
If you work with CI systems like Jenkins they can exactly do what you
wish...
Just define the version you like to use of Maven change the used version
in the build job and run the build. It will automatically download the
Maven version and use it...
> 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.
I suppose you are talking about prerequisites ?
This makes it hard to upgrade as we have several
projects to support and some will never be upgraded as they are older
branches.
Why ? Are those project maven plugin projects or "usual" application
build projects ?
Furthermore the question is which versions do they use at the moment ?
Why not updating Maven ...just do some tests build in a Jenkins and
afterward simply change it..?
> Is this feature on the Maven radar?
Not that i know...but i have to admit that i didn't check the jira for
that...But of course you can create a jira issue for this...
From my perspective i have my doubts to support such thing...
Kind regards
Karl Heinz Marbaise
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
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
