[jboss-jira] [JBoss JIRA] (WFLY-3151) Failure to start jboss-cli.sh due to space in the startup path

[ https://issues.jboss.org/browse/WFLY-3151?page=com.atlassian.jira.plugin.... ] David Lloyd updated WFLY-3151: ------------------------------ Description: The CLI startup script needs to be modified to process arguments like standalone.sh and friends to, to be tolerant of spaces in the original arg list. Original report: Sent email to wildfly-dev: {noformat} Java EE 7 CI job on WildFly trunk is failing: https://arungupta.ci.cloudbees.com/job/Java%20EE%207%20Samples%20on%20Wil... Here is the error message: Started 45 of 56 services (22 services are lazy, passive or on-demand) [0m+ wildfly-8.0.1.Final-SNAPSHOT/bin/jboss-cli.sh --connect '--commands=/subsystem=messaging/hornetq-server=default:write-attribute(name=journal-type,value=NIO),:reload(admin-only=false)' Error: Could not find or load main class EE Process leaked file descriptors. See http://wiki.jenkins-ci.org/display/JENKINS/Spawning+processes+from+build for more information Build step 'Execute shell' marked build as failure {noformat} David responded: {noformat} Looks like a possible regression in standalone.sh due to there being a space in the startup path. As a workaround you could change your workspace name from "Java EE 7 Samples on WildFly-cb" to e.g. "java-ee-7-samples-on-wildfly-cb" or similar (with no spaces). {noformat} was: Sent email to wildfly-dev: -- cut here -- Java EE 7 CI job on WildFly trunk is failing: https://arungupta.ci.cloudbees.com/job/Java%20EE%207%20Samples%20on%20Wil... Here is the error message: Started 45 of 56 services (22 services are lazy, passive or on-demand) [0m+ wildfly-8.0.1.Final-SNAPSHOT/bin/jboss-cli.sh --connect '--commands=/subsystem=messaging/hornetq-server=default:write-attribute(name=journal-type,value=NIO),:reload(admin-only=false)' Error: Could not find or load main class EE Process leaked file descriptors. See http://wiki.jenkins-ci.org/display/JENKINS/Spawning+processes+from+build for more information Build step 'Execute shell' marked build as failure -- cut here -- David reponded: -- cut here -- Looks like a possible regression in standalone.sh due to there being a space in the startup path. As a workaround you could change your workspace name from "Java EE 7 Samples on WildFly-cb" to e.g. "java-ee-7-samples-on-wildfly-cb" or similar (with no spaces). -- cut here -- -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira