Upgrading Oxygen XML Editor plugin

From time to time, upgrade and patch versions of Oxygen XML Editor plugin are released to provide enhancements that fix problems, and add new features.

What is Preserved During an Upgrade?

When you install a new version of Oxygen XML Editor plugin, some data is preserved and some is overwritten. If there is a previous version of Oxygen XML Editor plugin already installed on your computer, it can coexist with the new one, which means you do not have to uninstall it.

If you install over a previously installed version:

  • All the files from its install directory will be removed, including any modification in document type (framework) files, XSLT stylesheets, XML catalogs, and templates.
  • All global user preferences are preserved in the new version.
  • All project preferences will be preserved in their project files.
  • Any custom frameworks that were stored outside the installation directory (as configured in Document type associationsLocations) will be preserved and will be found by the new installation.

If you install in a new directory.

  • All the files from the old install directory will be preserved, including any modification in document type (framework) files, XSLT stylesheets, XML catalogs, and templates. However, these modifications will not be automatically imported into the new installation.
  • All global user preferences are preserved in the new version.
  • All project preferences will be preserved in their project files.
  • Any custom frameworks that were stored outside the installation directory (as configured in Document type associationsLocations) will be preserved and will be found by the new installation.

Upgrading the Eclipse Plugin

  1. Uninstall the current version of Oxygen XML Editor plugin.
  2. Download and install the new version using the appropriate instructions for your platform and the installation method you chose.
  3. Restart the Eclipse platform.
  4. Start the Oxygen XML Editor plugin to ensure that the application can start and that your license is recognized by the upgrade installation.
  5. If you are upgrading from a minor version to a major version (for example, from 16.1 to 17.0) and you did not purchase a Maintenance Pack that covers the new major version (17.0), you will need to enter a new license for the new version (17) into the registration dialog box that is displayed when the plugin is started.

Was this helpful?