Migrating from a previous qooxdoo version to a current release often requires nothing more than just running the migration job in your application. Yet, some changes between releases may involve manual modifications as detailed in the migration guide of each individual release. The following guide cover both cases.
If you are migrating from a legacy verison of qooxdoo to 1.4.2, namely from a 0.8.2 or prior release, please do a two-step migration to 1.4.2. Firstly, migrate to qooxdoo 0.8.3, following the instructions in the corresponding manual. You will need a qooxdoo 0.8.3 SDK to go through the process, so fetch one from the download location. This is necessary as there have been major changes in qooxdoo which require the infrastructure of the intermediate version to bridge. Then, follow the remaining steps in this document.
You might want to create a backup of your application files first. The migration process changes source files in place, modifying your code base.
Then change to your application's top-level directory and invoke the command
Follow the instructions of the migration script, particularly allow the cache to be deleted. For more information about this script, see the corresponding job description.
Check the migration.log which is created during the run of the migration script. Check all hints and deprecation warnings in the log and apply them to your code.
You now have an up-to-date source tree in your application. Run
to check that the generation process goes through and test your application in the browser.