Changes to Nexus Repository Core codebase

post by montag on Feb 6, 2025

With version 3.77.0 Nexus Repository has become “Community Edition” with the changes/restrictions described by Sonatype.

Brain Fox is mentioning the following in his blog post ( Introducing Nexus Repository Community Edition: Enhanced features for growing teams):

“It’s important to note that our open source EPL core (OSS) is not and has not changed. You can still benefit from the exact same core functionality and formats (apt, Maven, raw) that have been available for more than a decade. Most free users will likely transition to the more feature-rich Community Edition, but those who prefer to use the OSS tier are welcome to do so. We simply want to provide a clear path to additional capabilities and a greater degree of reliability for those seeking it.”

Unfortunately, there is no more information on the future of the OSS:

• will there be new versions for OSS be available? As binaries or only as source code?
• what will new OSS versions contain (bug fixes, security fixes, features)?
• will Sonatype actively participate on changes for new OSS version?
• can Nexus users easily update from the latest “Sonatype OSS 3.76.1” version to the new “Open Source OSS 3.X” version?

Thanks in advance,

Rainer

• OSS To community edition upgrade help

post by montag on Feb 6, 2025

Hello Jonathan,

thanks for the reply.

As OSS will no longer be actively maintained, the answer to my question in the subject topic is “Yes”. As you said an unsettling situation, but I have now clarity on the OSS/CE/Pro tiers to decide on how to continue with our existing OSS-based installation.

Greetings,

Rainer

post by Roland_KL on Feb 6, 2025

so, we have an orphaned OSS version now and a resetricted CE ?

rather hard/rude step to cripple something to 100000 components, especially when there is no easy way to determine the number of components in use in the OSS install.

i am not amused. i do administration of some nexus and now have a problem. and i’m also not amused that there wasn’t some more open/clear statement/note on the 100000/200000 limit.

for example here Sonatype Nexus Repository | Leading Binary Repository Manager - no mention of that new limit.

post by asuch on Feb 6, 2025

Hi Rainer, diving into each of your questions:

• The open source codebase (Nexus Repository Core) has always been available to the community and will remain as source code on GitHub. Nexus Repository OSS has been sunset and replaced with Nexus Repository Community Edition, from 3.77 onwards all binary bundles are Community Edition.
• The open source codebase (Nexus Repository Core) will continue to be updated. It receives code changes whenever we do Nexus Repository Community Edition/Pro releases. Nexus Repository Core will contain bug fixes, security fixes, and occasional new features.
• The Sonatype Open Source Community Handbook outlines how we accept contributions for all Sonatype Open source projects Contributing to a Project | Sonatype Open Source Community Handbook
• The direct upgrade path is from 3.76 to 3.77 (OSS binary to Community Edition binary). Nexus Repository Core is available to compile, because Core lacks some features included in OSS (and Community Edition) any migration would require some manual steps.

post by mprescott on Feb 6, 2025

@Roland_KL, we definitely don’t want you to be wondering if you’re over or below the limits before upgrading from the OSS binary to Community Edition. There’s a usage dashboard in the OSS edition binary that will tell you current and recent historical usage levels. It’s something we added in March of last year, in version 3.66.

In terms of clear communication about the Community Edition limits, thanks for your feedback about our Repository product page. We do want people to know how they work, which is why they were mentioned in the original blog post that announces Community Edition.

We believed that most people directly affected in the short term would be existing users upgrading, so we mention them in the 3.77.0 release notes, and on the Docker Hub page for our containerized version, both of which point to the more detailed description in our documentation.

post by Roland_KL on Feb 6, 2025

thank you for explaining. i will have a look at version 3.66+. as that is an internal nexus server, we are some version below that.

post by robross0606 on Aug 22, 2025

I think the problem here is the announcement from Brain Fox feels intentionally obtuse and almost meant to confuse people into upgrading to Community.

It’s important to note that our open source EPL core (OSS) is not and has not changed. You can still benefit from the exact same core functionality and formats (apt, Maven, raw) that have been available for more than a decade. Most free users will likely transition to the more feature-rich Community Edition, but those who prefer to use the OSS tier are welcome to do so. We simply want to provide a clear path to additional capabilities and a greater degree of reliability for those seeking it.

IMO, this isn’t true at all but he hides behind what was most likely very careful word choice like “same core functionality”. The truth is that OSS is available as raw code only and there is no reasonable/safe/documented way to upgrade a prior OSS version to the latest OSS version. The only documented upgrade path is from OSS to Community. The communication has been disingenuous from the start. Just be straight with people and let them make educated decisions.