1. #1
    Sencha Premium Member twasink's Avatar
    Join Date
    Oct 2012
    Location
    Brisbane, Australia
    Posts
    82
    Vote Rating
    8
    twasink will become famous soon enough

      0  

    Default [4.2.0-489] Upgrading from 4.2.0-265 and Sencha Cmd 3.0.2.288

    [4.2.0-489] Upgrading from 4.2.0-265 and Sencha Cmd 3.0.2.288


    What's the recommend process for upgrading from the previous beta releases of ExtJS 4.2 and Sencha Cmd (4.2.0-265 and 3.0.2.288, respectively) to the current releases (4.2.0-489 and 3.1.130)?

    As a test, I created a brand new app using the previous versions. When I try to do 'sencha app build' with the new Sencha CMD, it tells me to upgrade, but when I try to upgrade, it tells me that's not supported.

    Example output:

    Code:
    $ sencha-3.0.2.288 -sdk ext-4.2.0.265 generate app TestApp test_app
    Sencha Cmd v3.0.2.288
    [ creates new application ]
    $ cd test_app
    $ sencha-3.0.2.288 app build
    Sencha Cmd v3.0.2.288
    [ builds successfully ]
    $ sencha-3.1.0.130 app build
    Sencha Cmd v3.1.0.130
    [ERR] The app was last modified by an older version of Sencha Cmd (3.0.2.288). Please run 'sencha app upgrade' to update.
    [ERR] Application Cmd version mismatch.
    $ sencha-3.1.0.130 app upgrade -path ../ext-4.2.0.489/
    Sencha Cmd v3.1.0.130
    [INF] 
    [INF] init-plugin:
    [INF] 
    [INF] init-plugin:
    [INF] Invoking plugin (/Users/robertdw/tmp/extjs_upgrade/test_app/.sencha/app/plugin.xml) - supported targets: -before-app-upgrade
    [INF] 
    [INF] -before-app-upgrade:
    [INF] Invoking plugin (/Users/robertdw/tmp/extjs_upgrade/test_app/.sencha/app/plugin.xml) - supported targets: app-upgrade
    [INF] 
    [INF] cmd-root-plugin.init-properties:
    [INF] 
    [INF] init-properties:
    [INF] 
    [INF] init-sencha-command:
    [INF] 
    [INF] init:
    [INF] 
    [INF] -before-app-upgrade:
    [INF] 
    [INF] app-upgrade-impl:
    [ERR] Automated upgrade of 4.1.x apps to 4.2.x is currently unsupported.
    So how should one go about upgrading, then?

  2. #2
    Sencha Premium Member
    Join Date
    Jan 2013
    Posts
    42
    Vote Rating
    4
    Dev@QLP is on a distinguished road

      0  

    Default


    Quote Originally Posted by twasink View Post
    What's the recommend process for upgrading from the previous beta releases of ExtJS 4.2 and Sencha Cmd (4.2.0-265 and 3.0.2.288, respectively) to the current releases (4.2.0-489 and 3.1.130)?
    So how should one go about upgrading, then?
    You can't yet. According to the post about the beta version of Sencha Cmd (3.1.130), upgrading ExtJS 4.1 apps isn't supported yet. See here: http://www.sencha.com/forum/showthread.php?256446

    Quote from that post:
    PS - Please wait for the next release to test Sencha Cmd 3.1 with your Ext JS 4.1.x applications. This beta release is primarily targeted at Ext JS 4.2 but does support Sencha Touch 2.1 or higher. Please remember that this is a beta and the current official release is Sencha Cmd 3.0.2.

  3. #3
    Sencha Premium Member twasink's Avatar
    Join Date
    Oct 2012
    Location
    Brisbane, Australia
    Posts
    82
    Vote Rating
    8
    twasink will become famous soon enough

      0  

    Default


    I'm not trying to upgrade from 4.1; I'm trying to upgrade from the previous beta version of 4.2.0 - from 4.2.0-265 to 4.2.0-489.

    If there is no automated process, I need to find a manual approach. Right now, all I can see is "delete the application and build it again"

  4. #4
    Sencha Premium Member
    Join Date
    Jan 2013
    Posts
    42
    Vote Rating
    4
    Dev@QLP is on a distinguished road

      0  

    Default


    Oh duh. My bad. I haven't created an app with the 4.2 beta so I'm no help.

  5. #5
    Sencha Premium Member twasink's Avatar
    Join Date
    Oct 2012
    Location
    Brisbane, Australia
    Posts
    82
    Vote Rating
    8
    twasink will become famous soon enough

      0  

    Default


    In the end, I recreated the workspace and the app and re-imported our files. Now my UX guy needs to figure out the changes to the SASS structure, but other than that it's working.

Thread Participants: 1