maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jörg Buchberger (JIRA) <>
Subject [jira] Commented: (MNG-4577) support side by side installations of different maven versions
Date Wed, 03 Mar 2010 16:02:55 GMT


Jörg Buchberger commented on MNG-4577:

You are right, Benjamin. This works.  :-)
How do _you_ handle this in practice, though?

ATM, I see two ways ... by having the bin-directory of my most used Maven version always in
the PATH and ...

1) whenever I want to use another version I use "SET PATH=...;%PATH%" before calling "mvn

2) in projects where I know I need to use another version of Maven I put a batchfile named
"mvn.bat" containing a direct call to the desired mvn.bat

If you have a better or simply different approach to this, I'd really appreciate it, if you
share it here. Thanks!!  :-)

> support side by side installations of different maven versions
> --------------------------------------------------------------
>                 Key: MNG-4577
>                 URL:
>             Project: Maven 2 & 3
>          Issue Type: Improvement
>          Components: Bootstrap & Build, Command Line
>    Affects Versions: 2.0.11, 2.2.1, 3.0-alpha-6
>         Environment: Windows XP / Vista / 7
>            Reporter: Jörg Buchberger
> If you like existing users to adopt new versions of Maven faster and if you like to gain
new users of Maven from the paranoid type of build dudes...
> then I suggest you allow different versions of Maven to be installed and used in parallel.
> For example one might have the latest stable release installed, but likes to give the
latest beta from another a branch a shot. I.e. you want to be able to do your work as usual
on top of the stable release, while building something on top of a beta/branch version of
Maven at the same time. This does not work (at least on Windows) - in fact, Maven won't even
startup or emit version info anymore, if two or more versions of Maven are installed in parallel.
> Another decent example is this:
> Have the latest stable release around and ready for your work on a daily basis, while
at the same time keeping around an ancient version of Maven for some complicated legacy projects
in maintenance mode. This is useful, if project management does not allow to invest time into
migrating build configuration and subsequent testing of its results.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message