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 environment variables (especially PATH, java and maven home), when using a user/global settings.xml it should be valid for all versions (it usually is) or specify a unique file for each environment with the -s flag. Also make sure to specify the full path to the mvn launcher. Some plugins like maven release plugin also prefer if you set the correct M2_HOME env variable. When sharing the local maven cache, it usually works across different maven versions, just be careful when using it in parallel (using one cache per executor is sometimes more robust). Gruss Bernd -- http://bernd.eckenfels.net ________________________________ Von: Nitish Mittal <mittal.nitish2...@gmail.com> Gesendet: Thursday, January 7, 2021 6:18:57 PM An: users@maven.apache.org <users@maven.apache.org> Betreff: Fwd: Maven 3.6.3 configuration enquiry 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 co-exist. Secondly, i see there are 2 improvement issues in release notes, can you please halp me to know if we need to make those changes in our user settings file? or the project settings file? Thanks Nitish Mittal
