Documentation Nexus IQ Server 1.23

Our documentation site has moved. For the most current version, please see http://help.sonatype.com

18.7. Migrating to Different Component Versions

If you determine that a component upgrade is required to avoid a security or license issue or a policy violation, after reviewing your component usage, Sonatype CLM for Eclipse can be used to assist you in the necessary refactoring.

NOTE
This feature relies on the project being a Maven project.

The first step to start the migration is to select a newer version for the component in the visualization chart. An example is displayed in Figure 18.10, “Migrating to a Newer Component Version”.

figs/web/ide-eclipse-migrate-select.png

Figure 18.10. Migrating to a Newer Component Version


Once you have selected a different version than the one currently used, the Migrate button will become active. Pressing the button opens a dialog that assists you in the migration to the newer component. The complexity of this task varies considerably from project setup to project setup. The migration wizard is able to detect circumstances such as the component being a transitive dependency or versions managed in a property.

The simplest flow is when a dependency version can be applied, and the result is a single dialog like the one displayed in Figure 18.11, “Applying a Dependency Version Upgrade”.

figs/web/ide-eclipse-migrate-upgrade-version.png

Figure 18.11. Applying a Dependency Version Upgrade


If the version is managed in a property, the initial screen from Figure 18.12, “Selecting Dependency Version or Property Upgrade” allows you to select if you want to continue with a property upgrade, or perform a replacing version upgrade.

figs/web/ide-eclipse-migrate-upgrade-property.png

Figure 18.12. Selecting Dependency Version or Property Upgrade


Once you have selected to perform a property upgrade, you will be able to apply it in the next screen, Refactoring, visible in Figure 18.13, “Applying a Property Upgrade”.

figs/web/ide-eclipse-migrate-upgrade-property-apply.png

Figure 18.13. Applying a Property Upgrade


The Refactoring screen features navigation tools allowing you to view all potential changes in the dialog, and step through them one by one before deciding to continue.

After you have completed the refactoring of your project files, you should perform a full build, as well as a thorough test, to determine that you can proceed with the new version in your development.

Typically smaller version changes will have a higher chance of working without any major refactorings, or adaptations, of your code base and projects, while larger version changes potentially give you more new features or bug fixes.

Your release cycle, customer demands, productions issues and other influencing factors, will determine your version upgrade choices. You might decide a multi-step approach, where you do a small version upgrade immediately to resolve current issues and then work on the larger upgrade subsequently to get the benefits of using a newer version. Or, you might be okay with doing an upgrade to the latest available version straight away. Potentially, a combination of approaches in different branches of your source code management system is used to figure out the best way of going forward with the upgrade.

Sonatype CLM for Eclipse and other tools of the Sonatype CLM suite can assist you through the process of upgrading, as well as monitoring, the applications after upgrade completion.