Success! Looks like we've fixed this one. According to our records the fix was applied for SDKTOOLS-173 in 3.0.0 Sprint 7.
  1. 29 Sep 2012 12:02 PM #1
    powellke
    powellke is offline
    Ext JS Premium Member powellke's Avatar
    Join Date
    Sep 2008
    Location
    Huntsville, AL
    Posts
    37
    Vote Rating
    4
    powellke is on a distinguished road
      0  
    Send a message via Skype™ to powellke

    Default sencha ant production build does not work for Ext JS apps

    sencha ant production build does not work for Ext JS apps


    I installed 181 and created a new app (using 4.1.2a sdk)

    Code:
    sencha generate app TestApp c:\projects\TestApp
    Then, I went to the c:\projects\TestApp folder and ran

    Code:
    sencha ant production build
    and got this response:

    Code:
    Sencha Cmd v3.0.0.181
[ERROR]         Target "production" does not exist in the project "@@@".
    If I use the old command
    Code:
    sencha app build production
    it doesn't give me an error, but it also doesn't result in a production folder under the build folder; just a folder name TestApp. The only files that get copied to the build\TestApp folder are index.html and all-classes.js.

    Am I missing a step?
    Reply With Quote Reply With Quote
  2. 29 Sep 2012 12:34 PM #2
    dongryphon
    dongryphon is offline
    Sencha - Ext JS Dev Team dongryphon's Avatar
    Join Date
    Jul 2009
    Posts
    1,033
    Vote Rating
    57
    dongryphon is a jewel in the rough dongryphon is a jewel in the rough dongryphon is a jewel in the rough
      0  

    Default


    Thanks for the report! I have opened a bug in our bug tracker.
    Reply With Quote Reply With Quote
  3. 29 Sep 2012 12:35 PM #3
    dongryphon
    dongryphon is offline
    Sencha - Ext JS Dev Team dongryphon's Avatar
    Join Date
    Jul 2009
    Posts
    1,033
    Vote Rating
    57
    dongryphon is a jewel in the rough dongryphon is a jewel in the rough dongryphon is a jewel in the rough
      0  

    Default


    The different environment options (e.g., "production") are still touch-specific in their handling, but we must have missed adding "no op" targets for them in the Ext JS side to allow the commands to execute.

    "sencha ant build" should work for both frameworks using the default environment for Sencha Touch.
    Don Griffin
    Ext JS Development Team Lead

    Check the docs. Learn how to (properly) report a framework issue and a Sencha Cmd issue

    "Use the source, Luke!"
    Reply With Quote Reply With Quote
  4. 29 Sep 2012 12:36 PM #4
    dongryphon
    dongryphon is offline
    Sencha - Ext JS Dev Team dongryphon's Avatar
    Join Date
    Jul 2009
    Posts
    1,033
    Vote Rating
    57
    dongryphon is a jewel in the rough dongryphon is a jewel in the rough dongryphon is a jewel in the rough
      0  

    Default


    I also transplanted your post from its original location on the announcement thread. Sorry for any confusion on that but we cannot link individual posts from a thread to our bug tracker.
    Don Griffin
    Ext JS Development Team Lead

    Check the docs. Learn how to (properly) report a framework issue and a Sencha Cmd issue

    "Use the source, Luke!"
    Reply With Quote Reply With Quote
  5. 4 Oct 2012 6:03 AM #5
    Curtis Fletcher
    Curtis Fletcher is offline
    Sencha User
    Join Date
    Mar 2009
    Location
    Reading, UK
    Posts
    33
    Vote Rating
    1
    Curtis Fletcher is on a distinguished road
      0  

    Default


    Now I've dug down into it I think my problem here:

    http://www.sencha.com/forum/showthread.php?244917-3.0.0.181-Ext-JS-4.1.1a-unable-to-disable-yui-compression

    I    s the same. I managed to discover your workaround during discovery however this doesn't solve my base problem which is that a testing build appears to be impossible. Is there a workaround to disable compression on an Ext JS build?
    Reply With Quote Reply With Quote