Repository Manager Feature Matrix
The table below provides detail for the various the complete range of Repository Manager features, as well as the corresponding solution (license) that provides access to them. Whether you're looking to upgrade, curious about a specific format, or just simply want a bird's-eye view of features, check back often as we update this table whenever new features are released. If you are an existing user of Nexus Repository Manager 2.x and are looking to understand the equivalent feature in 3.x, check out our Feature Equivalency article.
|Feature||2 OSS||2 Pro||3 OSS||3 Pro|
|Git Large File Storage (LFS)|
|OBR||See Below||See Below|
|P2||See Below||See Below|
|Smart Proxy||See Below||See Below|
|Upgrading 2x to 3x|
|Upload Third Party Artifacts via UI||limited||limited|
|Custom Metadata||See Below||See Below|
|Improved Backup & Restore|
|REST||See Below||See Below|
|Plugins||See Below||See Below|
|Open Source Integration|
|Auth Token Support|
|Custom Access Controls|
|Repo Targets / Content Selectors|
|Staging & Build Promotion||See Below|
|User Token Support|
If you have questions about a specific feature, contact email@example.com.
3.5 NXRM3 has support for Yum proxy and 3.8 has added support for Yum hosted repositories. Support for group repositories is at the top of our priority list. If there's anything you'd like to see specific to a revamped YUM hosted solution, feel free to let us know by commenting on the JIRA ticket requesting support.
We aim to provide support for every format available. However, we also have to prioritize according to the needs of our customers. If you want to see OBR supported, check out the Nexus Repository Manager JIRA project and add a comment with your support.
Like OBR, we plan to support P2, and really any format. However, because we prioritize based on feedback from our users, this one’s a little further down the list. If you want to see P2 supported, check out the Nexus Repository Manager Public JIRA project and add a comment with your support.
In an upcoming version of Nexus Repository Manager Pro we’ll be introducing a distributed replication approach that allows for simplified replication of content between repository manager instances.
Currently, this feature is a bit further down the list. If this is something your team needs, let us know by commenting on the story via the public, Nexus Repository Manager JIRA project.
The rumors of a REST-less Nexus Repository Manager aren’t completely accurate. In fact, our new Provisioning API powered by Groovy scripts provide a better mechanism for achieving the most common use case for REST -- automated provisioning of a system and/or onboarding new projects. However, we are planning to deliver REST endpoints in 2017, beginning with the most frequently requested use cases. Let us know what you are looking for via our public JIRA project.
We love your plugins, and the Nexus Repository user community has already started to develop some. In fact, there’s already an open source implementation of the apt format. If you’ve created a Nexus Repository Manager plugin, reach out to our Community Advocate, and we’ll help you through the process of getting it out to other Nexus Repository users. View the entire list of plugins at Nexus Exchange.
Stage & Build Promotion
We totally understand how much you loved the staging and promotion features in Nexus Repository Manager 2, and for a number of our users, we know it’s the stopping point for moving completely off of Nexus Repository Manager 2 to 3. However, like all Nexus Repository Manager 3 features, we don’t simply want to port the functionality from the previous version. In fact, this time we are taking a completely different approach. Because the deployment and delivery landscape has changed since we developed staging and promotion, we want to make sure it supports a modern supply chain with a full range of completely flexible and performant features. Until then, why not reach out and let us know what you’d like to see, maybe tell us what types of tools you’d like to see it integrated with.