I use https://github.com/takari/maven-wrapper which is being adopted
and merged into maven as a core plugin as part of maven v3.7.0.
For me it allows each git commit to control what version of maven to
use, the developer and cicd for the same commit will be using the same
version of maven as they
This (setting automatically of M2_HOME) does not work in all cases, especially
not if the launch script is not used (IDE or Maven Agents), but it would be
best to not set it, if not needed (agreed).
--
http://bernd.eckenfels.net
Von: Jörg Schaible
Gesendet:
Am Donnerstag, 7. Januar 2021, 20:23:27 CET schrieb Bernd Eckenfels:
> You did not say what build servers you use, but normally you can have many
> different maven versions installed in different directories. Usually CI
> servers are fine to pick one (some like Jenkins can even install them
>
Have you tried the Maven wrapper? https://www.baeldung.com/maven-wrapper
Delany
On Thu, 7 Jan 2021 at 20:26, Nitish Mittal
wrote:
> Hi team,
>
> We are already using maven 3.3.9 and for some projects we want to configure
> 3.6.3 in the same set of build agents. Can you please help me to
You did not say what build servers you use, but normally you can have many
different maven versions installed in different directories. Usually CI servers
are fine to pick one (some like Jenkins can even install them dynamically).
If you do it, you need to watch out for not using/inheriting
Hi team,
We are already using maven 3.3.9 and for some projects we want to configure
3.6.3 in the same set of build agents. Can you please help me to understand
if there would be any issue if both versions co-exist on the same set of
servers. Is there any setting that needs to be done for them to
