I was migrating our production JET app from 2.2.0 to 3.0.0. End-to-end migration process took probably around 1-2 hours - with testing. I think this is quick. JET migration is not hard if you follow developer guide instructions - B Oracle JET v2.x.x to v3.0.0 Tooling Migration.
Migration from 2.2.0 must be done in two steps:
1. Migration to 2.3.0 from 2.2.0
2. Migration to 3.0.0 from 2.3.0
Step 1: Migration to 2.3.0 from 2.2.0
- Execute sudo npm install generator-oraclejet@2.3.0 -g to update Oracle JET to 2.3.0
- Execute sudo yo oraclejet ChBJellyHouseInvoicingJET230 to generate brand new JET 2.3.0 application
- Copy html/js files from existing application src folder into new one
- Update JET version number in index.html:
- Update JET version number and add additional library references (as per JET Developer Guide) in main.js:
- Update same set of libraries and versions in main-release-paths.json:
- Execute sudo grunt build:release to verify in migrated app build process succeeds:
- Execute sudo grunt serve:release to run application:
Step 2: Migration to 3.0.0 from 2.3.0
- Execute sudo npm install generator-oraclejet@3.0.0 -g to update Oracle JET to 3.3.0
- Execute sudo npm uninstall grunt-oraclejet oraclejet-tooling
- Execute sudo npm uninstall grunt-bowercopy --save-dev
- Execute sudo npm install grunt-oraclejet@3.0.0 oraclejet-tooling@3.0.0 --save-dev
- Execute sudo npm install oraclejet@3.0.0 --save
- Execute sudo npm uninstall bower -g to remove Bower, it is not needed anymore from JET 3.0.0
- Remove the following file from your system: scripts/grunt/config/bowercopy.js
- If you have no third-party dependencies remaining in your bower.json file, remove it
- Update JET version number in index.html:
- Update JET version number and add additional library references (as per JET Developer Guide) in main.js:
- Update same set of libraries and versions in main-release-paths.json:
- Execute sudo grunt build:release, most likely you will face error. Same was documented by someone on OTN Forum - v3.0.0 - Error with Grunt build and serve tasks with initConfig() in Gruntfile.js:
- To fix this error, add oraclejet-build.js and oraclejet-serve.js into scripts/grunt/config (you can copy these files from newly generated JET 3.0.0 app):
Migration from 2.2.0 must be done in two steps:
1. Migration to 2.3.0 from 2.2.0
2. Migration to 3.0.0 from 2.3.0
Step 1: Migration to 2.3.0 from 2.2.0
- Execute sudo npm install generator-oraclejet@2.3.0 -g to update Oracle JET to 2.3.0
- Execute sudo yo oraclejet ChBJellyHouseInvoicingJET230 to generate brand new JET 2.3.0 application
- Copy html/js files from existing application src folder into new one
- Update JET version number in index.html:
- Update JET version number and add additional library references (as per JET Developer Guide) in main.js:
- Update same set of libraries and versions in main-release-paths.json:
- Execute sudo grunt build:release to verify in migrated app build process succeeds:
- Execute sudo grunt serve:release to run application:
Step 2: Migration to 3.0.0 from 2.3.0
- Execute sudo npm install generator-oraclejet@3.0.0 -g to update Oracle JET to 3.3.0
- Execute sudo npm uninstall grunt-oraclejet oraclejet-tooling
- Execute sudo npm uninstall grunt-bowercopy --save-dev
- Execute sudo npm install grunt-oraclejet@3.0.0 oraclejet-tooling@3.0.0 --save-dev
- Execute sudo npm install oraclejet@3.0.0 --save
- Execute sudo npm uninstall bower -g to remove Bower, it is not needed anymore from JET 3.0.0
- Remove the following file from your system: scripts/grunt/config/bowercopy.js
- If you have no third-party dependencies remaining in your bower.json file, remove it
- Update JET version number in index.html:
- Update JET version number and add additional library references (as per JET Developer Guide) in main.js:
- Update same set of libraries and versions in main-release-paths.json:
- Execute sudo grunt build:release, most likely you will face error. Same was documented by someone on OTN Forum - v3.0.0 - Error with Grunt build and serve tasks with initConfig() in Gruntfile.js:
- To fix this error, add oraclejet-build.js and oraclejet-serve.js into scripts/grunt/config (you can copy these files from newly generated JET 3.0.0 app):
No comments:
Post a Comment