Upgrading to Nexus Repository 3.71.0 and Beyond
Nexus Repository 3.70.0 was the final release to include our legacy OrientDB embedded database alongside H2 and PostgreSQL. It was also the final release to include support for Java 8 and 11. From release 3.71.0, you must migrate to an H2 or PostgreSQL database and Java 17. The topics below provide detailed upgrade paths for those migrating to 3.71.0 and beyond.
Before proceeding, you must know the following information:
Current database (PostgreSQL, OrientDB, or H2)
If you are unsure what database you are currently using, see our documentation on determining your current database.
Current Nexus Repository version
Current Java version (Java 8, 11, or 17)
Once you know the above information, use the sections below to navigate to your specific upgrade path.
Find Your Upgrade Path
Use the table below to find your upgrade instructions.
Current Database | Current Nexus Repository Version | Current Java Version | Upgrade Instructions |
|---|---|---|---|
PostgreSQL | Any | Java 17 | No additional actions; follow normal upgrade procedures |
PostgreSQL | Any | Java 8/11 | Upgrade to Java 17 while upgrading to 3.71.0+ following normal upgrade procedures |
H2 | 3.70.x | Java 17 | No additional actions; follow normal upgrade procedures |
H2 | 3.70.x | Java 8/11 | Upgrade to Java 17 while upgrading to 3.71.0+ following normal upgrade procedures |
H2 | 3.69.0 | Java 17 | Specific Upgrade instructions for 3.69.0 deployments on H2 and Java 17 |
H2 | 3.69.0 | Java 8/11 | Specific Upgrade instructions for 3.69.0 deployments on H2 and Java 8/11 |
H2 | 3.68.x or earlier | Java 8/11 | Specific Upgrade instructions for pre-3.69.0 deployments on H2 and Java 8/11 |
OrientDB | 3.70.x | Java 8/11 | Specific Upgrade instructions for 3.70.x deployments on OrientDB and Java 8/11 |
OrientDB | 3.69.x or earlier | Java 8/11 | Specific Upgrade instructions for 3.69.0 and earlier deployments using OrientDB and Java 8/11 |
Frequently Asked Questions
This section covers answers to some of our most frequently asked questions related to upgrading to 3.71.0+.
Do I have to buy a Pro license to upgrade to version 3.71.0+?
As of 3.70.0, all users can migrate to an H2 database and then upgrade to 3.71.0+. You only need a Pro license if you plan to migrate to a PostgreSQL database.
Is OrientDB going away completely? When?
There is no current sunset date for OrientDB; however, it is not supported for or included in Nexus Repository versions 3.71.0 and beyond.
We will continue to support OrientDB in our 3.70.x release line, including releasing patches to the 3.70.x line. You can download the latest 3.70.x release and latest 3.70.x database migrator utility from our 3.70.x downloads page.
OrientDB is now considered in Extended Maintenance, which means that we will not release new features for OrientDB or to our Nexus Repository 3.70.x line.
Do I have to get off of OrientDB to keep using Nexus Repository?
While we encourage everyone to migrate off of OrientDB as soon as possible, we will continue to support OrientDB in our 3.70.x release line. We will continue to release 3.70.x version updates with bug fixes; however, we will not be adding new features to our 3.70.x line or for OrientDB.
You can download the latest 3.70.x release and the latest 3.70.x database migrator utility from our 3.70.x downloads page.
Why did we remove OrientDB from versions 3.71.0+?
As detailed in our Nexus Repository 3 sunsetting information, Sonatype is invested in continually improving our solutions to take advantage of newer, more advanced technologies. As such, we are strategically moving away from legacy technologies like OrientDB and investing in supporting newer database options. Moreover, Sonatype has observed data integrity problems in some deployments using OrientDB.