Feature Equivalency Matrix
Feature Equivalency Matrix
Nexus Repository 3 represents a complete rewrite of architecture and functionality. Some features from Nexus Repository 2 are no longer available in Nexus Repository 3. The matrix below details features replaced or removed in Nexus Repository 3.
| Repository 2 Feature | Equivalent | Note |
|---|---|---|
| Analytics | ||
| Automatic Routing | ||
| Browse Remote | ||
| Maven Settings | ||
| Non-Sonatype Repository Plugins | Nexus Repository 2 plugins are not compatible with Nexus Repository 3 architecture | |
| System Feeds | We have no plans to include System Feeds as the data is specific to the instance where it was generated. Near equivalent functionality is available through auditing and webhooks. |
|
| Virtual Repository (Shadow Repository) | This feature is not carried over to Nexus Repository 3. | |
| Atlassian Crowd | Verify the Crowd application is configured to accept connections from Nexus Repository 3 | |
| Branding | The branding configuration is not be upgraded automatically. | |
| Custom Metadata | Nexus Repository 3 can associate arbitrary data with any component in any repository format via its tagging feature. However, no automated way to migrate Nexus Repository 2 custom metadata exists. See tagging |
|
| Enterprise LDAP Servers | Individual LDAP Server configurations are upgraded. Backup Mirror servers are not upgraded. | |
| IQ Server Configuration | The wizard clones the IQ Server configuration. The quarantine data is cloned to work with repositories upgraded to Nexus Repository 3. | |
| Local User Accounts | ||
| LDAP | ||
| Manual Routing Rules | See Routing Rules | |
| Mapped User and Roles | ||
| Privileges | Privilege names are changed during the upgrade. Transitive group privileges are implemented differently. In Nexus Repository 2, privileges to a group repository are inherited to member repositories of that group repository. In Nexus Repository 3 this is not the case. After the upgrade, you may need to manually assign privileges for individual repositories. See Nexus Repository 2 KB article |
|
| Procurement | Procurement is deprecated. The Repository Firewall solution provides more comprehensive features. See Repository Firewall |
|
| Proxy Repository of maven.oracle.com | See the KB article | |
| #### Repository Formats - Bower Repositories - Maven Repositories - npm Repositories - NuGet Repositories - NuGet API Keys - p2 and p2 Update Site Repositories - PyPI Repositories - RubyGems Repositories - YUM Repositories |
||
| Repository Health Check Analysis (RHC) | See Repository Firewall | |
| Repository Targets | See content selectors | |
| REST API | Nexus Repository 2 REST APIs are not compatible with Nexus Repository 3. See REST API |
|
| Roles | ||
| RUT Auth Realm | This is not upgraded automatically as it is a security concern when enabled. Configure this manually inside Nexus Repository 3 when you are confident that Nexus Repository 3 access is protected. |
|
| Security | ||
| Server Settings | ||
| Smart Proxy | See Content Replication | |
| Site Repositories | Renamed as the raw repository format in Nexus Repository 3 | |
| SSL Certificates | SSL certificates trusted in the UI will be upgraded, but not all of them apply. Review trusted certificates after the upgrade. The wizard does not migrate the certificate that Nexus Repository uses for its own HTTPS connection. | |
| Staging | Nexus Repository 2 Staging is replaced with component tagging to manage workflow. See Staging |
|
| User Token | See the prerequisites for upgrading for information on how to include pre-existing user tokens from your Nexus Repository 2 instance when upgrading to Nexus Repository 3. |