SONATYPE NEXUS REPOSITORY | VERSION 2
Nexus Repository Manager 2 is Now End-of-Life
Action Required: All versions on Nexus Repository Manager 2 are no longer supported. Upgrade to a supported version.
Upgrade to a Supported Version of Nexus Repository
As of June 30, 2024, Sonatype Nexus Repository Manager 2 has reached End-of-Life (EOL) status. This means it no longer receives security updates, bug fixes, or new features. We recommend upgrading to the latest version of Nexus Repository 3 immediately to limit risk exposure.
Nexus Repository 3 is a modern, performant architecture that introduces several features and improvements not available in Nexus Repository 2. Upgrade to take advantage of format support for the full ecosystem, modern REST APIs, content selectors, custom tagging, and more.
Upgrade for Expanded Capabilities
Feature |
Capabilities |
Benefits |
|---|---|---|
| Broader Repository Format Support |
Nexus Repository 3 supports more repository formats natively, such as Docker, npm, NuGet, YUM, PyPI, Hugging Face, RubyGems, and raw repositories, in addition to Maven. Some formats (like Docker, Hugging Face, and raw) are not available in Nexus Repository 2, and others (like YUM) are supported in a more robust, native way in Nexus Repository 3.
|
Work in the tools you use most to streamline developer efficiency.
|
| Content Selectors |
Powerful and flexible ways to control access and manage content through Content Selectors: Repository targets from Nexus Repository 2 are replaced by content selectors in Nexus Repository 3, providing flexible ways to control access and manage content.
|
Fine-grained RBAC without per-repo sprawl, resulting in fewer repos to maintain and approximately 5-10 hours less per week on admin toil.
|
| Blob-store architecture |
Improved Storage Model: Nexus Repository 3 uses a blob store architecture for content storage, which is more scalable and supports a wider range of storage backends, including cost-effective cloud object storage. Nexus Repository 2 stores content directly on the filesystem in a less flexible way.
|
Cheaper, elastic object storage with the ability to move TBs from SAN/NAS to S3/GCS/Azure Blob for faster cleanup tasks, while paying only a third of the cost per GB/month.
|
| Modern REST API + webhooks |
Nexus Repository 3 provides a new REST API that allows for flexible access of all content, and complete configuration automation.
|
Full automation in CI/CD pipelines that cuts manual release steps, reduces wait time per build and deployment.
|
| Tagging & custom metadata |
Component Tagging and Flexible Staging: Staging in Nexus Repository 3 is based on component tagging and REST APIs, allowing for more flexible, CI/CD-integrated workflows. In contrast, Nexus Repository 2 uses a static, Maven2-only staging suite that is less scalable and flexible. Nexus Repository 3’s approach supports multiple formats and is designed for modern DevOps pipelines, with tagging, metadata association, and external workflow management via REST APIs and CI/CD tools.
|
Governance and traceability with no extra DB that saves audit-prep hours and speeds incident triage.
|
| Health Check + Firewall |
Repository Health Check and Firewall: Nexus Repository 3 offers enhanced repository health check analysis and integrates with Repository Firewall for more comprehensive security features.
|
Proactive vulnerability gating that avoids at least one major "bad component" incident.
|
| Modern UX |
Modernized User Experience and UI: Nexus Repository 3’s UI and user experience are significantly improved and modernized compared to Nexus Repository 2.
|
Quicker self-service onboarding, freeing up your help-desk team.
|
| Legacy 2-style URLs |
Nexus Repository 3 can support legacy Nexus Repository 2-style repository URLs to ease migration for automation and CI tools.
|
Geo-redundant and secure cloud-native delivery with reduced friction that improves DR, compliance, and cloud portability.
|
Capabilities
| Feature | |
|---|---|
| Broader Repository Format Support |
Nexus Repository 3 supports more repository formats natively, such as Docker, npm, NuGet, YUM, PyPI, Hugging Face, RubyGems, and raw repositories, in addition to Maven. Some formats (like Docker, Hugging Face, and raw) are not available in Nexus Repository 2, and others (like YUM) are supported in a more robust, native way in Nexus Repository 3.
|
| Content Selectors |
Powerful and flexible ways to control access and manage content through Content Selectors: Repository targets from Nexus Repository 2 are replaced by content selectors in Nexus Repository 3, providing flexible ways to control access and manage content.
|
| Blob-store architecture |
Improved Storage Model: Nexus Repository 3 uses a blob store architecture for content storage, which is more scalable and supports a wider range of storage backends, including cost-effective cloud object storage. Nexus Repository 2 stores content directly on the filesystem in a less flexible way.
|
| Modern REST API + webhooks |
Nexus Repository 3 provides a new REST API that allows for flexible access of all content, and complete configuration automation.
|
| Tagging & custom metadata |
Component Tagging and Flexible Staging: Staging in Nexus Repository 3 is based on component tagging and REST APIs, allowing for more flexible, CI/CD-integrated workflows. In contrast, Nexus Repository 2 uses a static, Maven2-only staging suite that is less scalable and flexible. Nexus Repository 3’s approach supports multiple formats and is designed for modern DevOps pipelines, with tagging, metadata association, and external workflow management via REST APIs and CI/CD tools.
|
| Health Check + Firewall |
Repository Health Check and Firewall: Nexus Repository 3 offers enhanced repository health check analysis and integrates with Repository Firewall for more comprehensive security features.
|
| Modern UX |
Modernized User Experience and UI: Nexus Repository 3’s UI and user experience are significantly improved and modernized compared to Nexus Repository 2.
|
| Legacy 2-style URLs |
Nexus Repository 3 can support legacy Nexus Repository 2-style repository URLs to ease migration for automation and CI tools.
|
Benefits
| Feature | |
|---|---|
| Broader Repository Format Support |
Work in the tools you use most to streamline developer efficiency.
|
| Content Selectors |
Fine-grained RBAC without per-repo sprawl, resulting in fewer repos to maintain and approximately 5-10 hours less per week on admin toil.
|
| Blob-store architecture |
Cheaper, elastic object storage with the ability to move TBs from SAN/NAS to S3/GCS/Azure Blob for faster cleanup tasks, while paying only a third of the cost per GB/month.
|
| Modern REST API + webhooks |
Full automation in CI/CD pipelines that cuts manual release steps, reduces wait time per build and deployment.
|
| Tagging & custom metadata |
Governance and traceability with no extra DB that saves audit-prep hours and speeds incident triage.
|
| Health Check + Firewall |
Proactive vulnerability gating that avoids at least one major "bad component" incident.
|
| Modern UX |
Quicker self-service onboarding, freeing up your help-desk team.
|
| Legacy 2-style URLs |
Geo-redundant and secure cloud-native delivery with reduced friction that improves DR, compliance, and cloud portability.
|
Upgrade to Future-Proof Your Repo
On a Different Release?
Explore information across all Nexus Repository Manager releases.