Thank you for reporting this bug. We will make it our priority to review this report.
  1. #1
    Ext JS Premium Member itlogo's Avatar
    Join Date
    Mar 2008
    Posts
    30
    Vote Rating
    0
    itlogo is on a distinguished road

      0  

    Default "sencha app build package" not reading app.json

    "sencha app build package" not reading app.json


    I followed Robert Dougan's easy 1-2-3 article for using PhoneGap to wrap ST, and I'm having a problem at the step that calls the command, "sencha app build package." I changed my app.json to have:


    "buildPaths": {
    "testing": "build/testing",
    "production": "build/production",
    "package": "build/phonegap/www",
    "native": "build/native"
    },

    However, after running "sencha app build package", the packaged contents are put under "build/SenchaHello/package" (SenchaHello is the project name). The output of the command verifies the same:

    [INF] Successfully deployed your application to /Users/trung/Documents/Eclipse/SenchaHello/build/SenchaHello/package

    I've deleted and rebuilt the project several times just to verify I hadn't mucked anything up. With regards to the ST project, I haven't made any changes other than adding the cordova.ios.js file and changing the package path, as described by Robert's article.

    Thanks

  2. #2
    Sencha - Senior Forum Manager mitchellsimoens's Avatar
    Join Date
    Mar 2007
    Location
    St. Louis, MO
    Posts
    33,711
    Vote Rating
    436
    mitchellsimoens has much to be proud of mitchellsimoens has much to be proud of mitchellsimoens has much to be proud of mitchellsimoens has much to be proud of mitchellsimoens has much to be proud of mitchellsimoens has much to be proud of mitchellsimoens has much to be proud of mitchellsimoens has much to be proud of mitchellsimoens has much to be proud of

      0  

    Default


    Sencha Cmd does not use the buildPaths from app.json and I believe that has been fixed to remove that data. To do this now you can open .sencha/app/build-impl.xml and around line 190 you will see the 4 different targets. In the value of the <property> you should be able to control where things are built in to.
    Mitchell Simoens @SenchaMitch
    Sencha Inc, Senior Forum Manager
    ________________
    http://www.JSONPLint.com - Source to lint your JSONP!

    Check out my GitHub, lots of nice things for Ext JS 4 and Sencha Touch 2
    https://github.com/mitchellsimoens

    Think my support is good? Get more personalized support via a support subscription. https://www.sencha.com/store/

    Need more help with your app? Hire Sencha Services services@sencha.com

    Want to learn Sencha Touch 2? Check out Sencha Touch in Action that is almost in print!

    When posting code, please use BBCode's CODE tags.

  3. #3
    Ext JS Premium Member itlogo's Avatar
    Join Date
    Mar 2008
    Posts
    30
    Vote Rating
    0
    itlogo is on a distinguished road

      0  

    Default


    I don't see anything obvious regarding the output path for that target:

    <target name="package">
    <property name="args.environment" value="package"/>
    </target>

    However, in .sencha/workspace/sencha.cfg, I do see this:

    workspace.build.dir=${workspace.dir}/build/${app.name}

    But I don't see any way of specifying the complete target directory--even changing workspace.build.dir to build/phonegap/www, "sencha app build package" puts the contents in build/phonegap/www/package