How to Upgrade Nexus Repository Manager 3.0.2 to 3.1.0 or Later

At runtime, the repository manager picks up the default properties automatically. So if you update from OSS to PRO, PRO settings will persist (if a license is in place). Basically, any settings in nexus.properties will take precedence over nexus-default.properties.

Before Upgrading

Before you upgrade from 3.0.2 to 3.1.0, you’ll need to get familiar with the new disk layout for 3.1.0. It consists of a sonatype-work folder with a nested nexus3 directory containing all your content and configurations. Don’t modify your nexus-defaults.properties file. Instead, modify the nexus.properties file created in sonatype-work once you start version 3.1.0. 

Upgrading 3.0.2 to 3.1.0

Perform your upgrade as follows:

  1. Locate your 3.0.2 data directory.
  2. Locate your 3.0.2 application directory.
  3. Download and extract the distribution archive for 3.1.0 for your operating system.
  4. Stop running version 3.0.2 of your repository manager.
  5. Manually back up the contents of the $3.0.2-02/data to another location.
  6. Copy or move the contents of $3.0.2-02/data so they overwrite the contents of /sonatype-work/nexus3/ in 3.1.0.
  7. Create a nexus.properties file in /sonatype-work/nexus3/etc in 3.1.0.
  8. Copy the contents of $3.0.2-02/etc/org.sonatype.nexus.cfg to $3.1.0-04/../sonatype-work/nexus3/etc/nexus.properties.
  9. Remove any mention of nexus-edition or nexus-features in the 3.1.0 data directory, i.e. $3.1.0-04/../sonatype-work/nexus3/etc/nexus.properties.
  10. In $3.1.0-04/../sonatype-work/nexus3/etc/nexus.properties replace each ${karaf.etc} with ${jetty.etc} in the nexus-args property. E.g. nexus-args=${jetty.etc}/jetty.xml,${jetty.etc}/jetty-http.xml,${jetty.etc}/jetty-requestlog.xml.
  11. If you have made customizations in $3.0.2-02/etc/, you will need to manually re-apply these changes to 3.1.0-04.
  12. Start Nexus using the scripts in nexus-3.1.0-04/bin/, or your service.
Have more questions? Submit a request

0 Comments

Article is closed for comments.
Powered by Zendesk