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

["Hudson (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MNG-7199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17391154#comment-17391154 ] 

Hudson commented on MNG-7199:
-----------------------------

Build succeeded in Jenkins: Maven » Maven TLP » maven » MNG-7199 #4

See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-7199/4/

> MAVENHOME_CONFIG var in mvnlauncher script improperly handles two options at once
> ---------------------------------------------------------------------------------
>
>                 Key: MNG-7199
>                 URL: https://issues.apache.org/jira/browse/MNG-7199
>             Project: Maven
>          Issue Type: Bug
>          Components: Command Line
>            Reporter: Michael Osipov
>            Assignee: Michael Osipov
>            Priority: Major
>             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)