[MNG-7199] MAVENHOME_CONFIG var in mvnlauncher script improperly handles two options at once

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 4.0.0-alpha-2, 4.0.0
• Component/s: Command Line
• Assignee: Michael Osipov
• Reporter: Michael Osipov
• Created: 29/Jul/21 09:28
• Updated: 20/Oct/22 08:11
• Resolved: 01/Aug/21 18:01

Description

This variable sets:

-MAVENHOME_CONFIG=`echo "-Dclassworlds.conf=${MAVEN_HOME}/bin/m2.conf" "-Dmaven.home=${MAVEN_HOME}"`

We properly quote all other variables to avoid pitfalls like spaces, etc. Unfortunately, Bourne shell does not support arrays to this variable is passed as-is and spaces cannot be escaped. The command fails.
This variable needs to be replaced with one for ClassWorlds Conf file and Maven home is already present.

Windows command script properly handles spaces in the variables and passes to the java command.

Issue Links

• is related to: MNG-4559 MAVEN_OPTS are incorrectly resolved in Unix
• links to: GitHub Pull Request #518