Repository Manager 2 to 3 Feature Equivalency
Nexus Repository Manager 3 (available via the Nexus Repository 3 OSS or Pro Product license) represents a complete rewrite of architecture and functionality. As of version 3.1.x many of these features have a new, modern equivalency. However, there is not yet 1:1 parity with regard to features, and in some cases, that may be the case for some time. Please use the matrix below to plan any upgrades and/or installations.
Repository 2 Feature
Repository 3 Equivalent
These are settings under Administration → Server in Nexus Repository Manager 2
Please refer to the Security section
Local User Accounts
Names may change on upgrade from Nexus Repository Manager 2 to 3
Proxy Repository of
Maps to content selectors
Manual Routing Rules
|See Routing Rules|
We anticipate implementing an alternate feature that is applicable to any supported repository format.
We will consider similar optimization features like this in the future as warranted.
We are planning a set of instance-to-instance replication features.
The Procurement feature, which is limited to Maven in Nexus Repository 2, has been deprecated. Going forward, Sonatype's Nexus Firewall solution provides a far more robust and comprehensive set of features aimed at managing risky components via your repository.
Nexus Repository Manager 2.x Staging has been replaced with a more robust solution that relies on component tagging to manage workflow. See here for details.
Nexus Repository Manager 3 has the ability to associate arbitrary data with any component in any repository format via it's tagging feature. However, there is currently no upgrade mechanism which will preserve existing custom metadata from Nexus Repository Manager 2.
YUM proxy support is included in the Nexus Repository Manager 3.5.0 release and hosted support is included in the Nexus Repository Manager 3.8.0 release. Feature was completed in 3.11.0.
p2 and p2 Update Site Repositories
NuGet API Keys
This is called Raw repository format in Nexus Repository Manager 3
We have no plans to upgrade System Feeds as the data is specific to the instance where it was generated. Our roadmap includes improving auditing capabilities and adding webhooks into Nexus Repository Manager 3.1.
The Nexus Repository Manager 2 branding configuration will not be upgraded automatically. Nexus Repository Manager 3 uses the UI: Branding capability.
A Scripting API is available which may be suitable for some use cases, however, the Nexus Repository Manager 2 REST APIs are not compatible with Nexus Repository Manager 3. Our roadmap includes adding various REST API endpoints at a later date.
Non-Sonatype Repository Manager Plugins
Nexus Repository Manager 2 plugins are not compatible with Nexus Repository Manager 3 OSGI bundle architecture
SSL certificates trusted in the UI will be upgraded, but not all of them may be applicable to a new server. Trusted certificates should be reviewed after your upgrade. Upgrade does not include the certificate that Nexus Repository Manager uses for its own HTTPS connection, if present.
This little-used feature was removed in 3.15.
Nexus Repository OSS Servers
Nexus Repository Pro (Enterprise) Servers
Individual LDAP Server configurations will be upgraded. Backup Mirror servers will not be upgraded.
Mapped Users and Roles
After your upgrade, you will need to ensure your Crowd application is configured to accept connections from Nexus Repository Manager 3
Mapped User and Roles
See section on User Token Upgrade
IQ Server Configuration
Repository Health Check Analysis (RHC)
RUT Auth Realm
This will NOT be upgraded automatically. This feature can be a security concern when enabled. Configure this manually inside Nexus Repository Manager 3 when you are confident that Nexus Repository Manager 3 access is protected.