You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Michael Osipov (Jira)" <ji...@apache.org> on 2021/07/29 09:29:00 UTC
[jira] [Created] (MNG-7199) MAVENHOME_CONFIG var in mvnlauncher
script improperly handles two options
Michael Osipov created MNG-7199:
-----------------------------------
Summary: MAVENHOME_CONFIG var in mvnlauncher script improperly handles two options
Key: MNG-7199
URL: https://issues.apache.org/jira/browse/MNG-7199
Project: Maven
Issue Type: Bug
Components: Command Line
Reporter: Michael Osipov
Fix For: 4.0.x-candidate
This variable sets:
{noformat}
-MAVENHOME_CONFIG=`echo "-Dclassworlds.conf=${MAVEN_HOME}/bin/m2.conf" "-Dmaven.home=${MAVEN_HOME}"`
{noformat}
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.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)