You found a bug! We've classified it as
a bug in our system.
We encourage you to continue the discussion and to find an acceptable workaround while we work on a permanent fix.
Sencha cmd bash script fails when install path contains spaces
Sencha Cmd version(s) tested:
Steps to reproduce the problem:
- When the directory containing the sencha cmd tools has spaces in it, the "sencha" bash script fails. We have the cmd tools committed to git, then Jenkins runs it directly out of its workspace directory.
This occurs because the $BASEDIR variable in the "sencha" script is not properly quoted wherever used. The attached patch resolves the issue for both the Linux and OS X versions.
/home/myhome/jenkins/workspace with spaces/ $ sencha-cmd/sencha app build production
/home/myhome/jenkins/workspace with spaces/sencha-cmd/sencha: line 37: [: too many arguments
sed: /home/myhome/jenkins/workspace: No such file or directory
Unable to access jarfile /home/myhome/jenkins/workspace
Last edited by raztus; 20 May 2013 at 9:13 AM.
Reason: Clarify code block
Sounds pretty similar, but affects a different product (SenchaSDKTools-2.0.0-beta3 vs. Sencha Cmd 188.8.131.524).
Indeed but the ticket internally is also tied to Cmd 3.1 but will link the ticket to this thread also.
Originally Posted by raztus