Nexus Repository Manager 2.x to 3.x 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.

2.x Feature

3.x Equivalent

Note

Server Settings

(thumbs up)

These are settings under Administration -> Server in Nexus RepositoryManager  2.x

Security

(thumbs up)

Please refer to the Security section

Local User Accounts

(thumbs up)

 

Privileges

(thumbs up)

Names will change.

Roles

(thumbs up)

 

Maven Repositories

(thumbs up)

Refer to the limitations below.

Proxy Repository of maven.oracle.com

(error)

See article to help determine if you have this configured.

Repository Targets

(thumbs up)

Maps to content selectors.

Manual Routing Rules

(thumbs up)

 

Maven Settings

(error)

We anticipate implementing an alternate feature that is applicable to any supported repository format.

Automatic Routing

(error)

We will consider similar optimization features like this in the future as warranted.

Smart Proxy

(error)

Smart Proxy is being replaced by a much more powerful component fabric architecture.

Procurement

(error)

The Procurement feature, which is limited to Maven in Nexus Repository 2.x, 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.

Staging

(error)

Our roadmap includes a plan to replace Staging with a more robust solution that relies on component metadata to manage workflow. Contact your account manager for more details.

Custom Metadata

(error)

Our roadmap includes adding the ability to associate arbitrary data with any component in any repository format. Eventually, custom metadata from Nexus Repository Manager 2.x may be upgraded into this format.

YUM Repositories

(error)

Planned.

P2 and P2 Update Site Repositories

(error)

Future Consideration.

RubyGems Repositories

(thumbs up)

Included in Nexus Repository Manager 3.0.2

PyPI Repositories

(thumbs up) Included in Nexus Repository Manager 3.0.2

npm Repositories

(thumbs up)

 

NuGet Repositories

(thumbs up)

 

  NuGet API Keys

(thumbs up)  
Bower Repositories

(thumbs up)

 

Site Repositories

(thumbs up)

This is called Raw repository format in Nexus Repository Manager 3.x.

System Feeds

(error)

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.

Branding

(thumbs up)

The Nexus Repository Manager 2.x branding configuration will not be upgraded automatically. Brand Nexus Repository Manager 3.x using the UI: Branding capability.

REST API

(error)

A Scripting API is available which may be suitable for some use cases, however, the Nexus Repository Manager 2.x REST APIs are not compatible with Nexus Repository Manager 3.x. Our roadmap includes adding various REST API endpoints at a later date.

Non-Sonatype Repository Manager Plugins

(error)

Nexus Repository Manager 2.x plugins are not compatible with Nexus Repository Manager 3.x OSGI bundle architecture.

SSL Certificates

(thumbs up)

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.

Analytics

(thumbs up)

Analytics are an opt-in feature to help analyze usage patterns. Settings will not be upgraded.

LDAP

   

Nexus Repository OSS Servers

(thumbs up)

 

Nexus Repository Pro (Enterprise) Servers

(thumbs up)

Individual LDAP Server configurations will be upgraded. Backup Mirror servers will not be upgraded.

Mapped Users and Roles

(thumbs up)

 
     

Atlassian Crowd

(thumbs up)

After your upgrade, you will need to ensure your Crowd application is configured to accept connections from Nexus Repository Manager 3.x.

Mapped User and Roles

(thumbs up)

 

User Token

(thumbs up)

See section on User Token Upgrade

IQ Server Configuration

(thumbs up)

 

Repository Health Check Analysis (RHC)

(thumbs up)

 

RUT Auth Realm

(thumbs up)

This Will NOT be upgraded automatically. This feature can be a security concern when enabled. Configure this manually inside Nexus Repository Manager 3.x when you are confident that Nexus Repository Manager 3.x access is protected.

Have more questions? Submit a request

0 Comments

Article is closed for comments.
Powered by Zendesk