title: Sencha Cmd broken: Why does 'app build' ignore any command line parameters?
body: <p>I've upgraded Sencha cmd to v4 and I used to be able to build to a specific archive path and destination path. This was crucial as the build server removes the source code folder and archive path for each build. I had the paths output on the IIS server away from the build server, so that they are never lost.</p>
  
  <p>However, my build process is failing now as the path parameters supplied to the sencha cmd don't do anything.</p>
  
  <p>If I type:</p>
  
  <pre><code>Sencha help app build
  </code></pre>
  
  <p>I get the following help:</p>
  
  <pre><code>Syntax
  
  sencha app build [options] [environment] \
                             [destination] \
                             [archive]
  </code></pre>
  
  <p>But supplying these parameters has no effect to the location of the output.</p>
  
  <p>Can anyone point me to the documentation which shows if this has changed and how I rectify it. I can't find anything on the their site which shows how to build for production and have it output to separate paths. Also I'd like to know why the Sencha Tools change so much. This wreaks havoc on any existing build systems because things suddenly stop working.</p>
  
  <p>See below:</p>
  
  <pre><code>C:\Development\Projects\IEApp&gt;sencha app build --archive C:\temp\build\IEApp\bui
  ldarchive --destination C:\temp\build\IEApp\Destination --environment production
  </code></pre>
  
  <p>Everything builds ok, but the <strong>C:\temp\build</strong> folder is empty.</p>