Repository Management with Nexus
Since Nexus separates its configuration and data storage from the application, it is easy to upgrade an existing Nexus installation.
To upgrade Nexus, unpack the Nexus archive in the directory which
contains the existing Nexus installation. Once the archive is
unpacked, the new Nexus application directory should be a sibling to
If you have defined a symbolic link for the version of Nexus to use, stop the server and change that to point at the new Nexus application directory. When you start the new instance of Nexus it will read the existing repository configuration from the sonatype-work directory. Depending on the version you upgrade from and to, some maintenance tasks like rebuilding the internal indices can be necessary. Please refer to the upgrade notes of the new release for more information on this. In addition a review of the release notes can be very useful to get a better understanding of potential, additional steps required.
If you are using any additional plugins supplied by Sonatype, the new version of Nexus you downloaded will contain a newer version of the plugin. Be sure to copy the new version from the optional-plugins folder to the plugin-repository folder as documented in Section 19.1, “Managing Nexus Plugins” and restart Nexus.
Externally supplied plugins are updated by simply replacing the folder with the plugin with the new version.
This automatic upgrade of Nexus works for nearly all update ranges. All 2.x versions can directly upgrade to the latest version. All 1.x version can upgrade to 2.7.x maximum. If you need to upgrade from 1.x to a newer version, you need to perform an intermediate upgrade step to a 2.x version.
The same upgrade process can be used to change from the open source to the professional version of Nexus.