Nexus Repository 3.6.0 Released

Michael Prescott: Nexus Repository with Yum Support

Michael Prescott: Nexus Repository

The Repo team is pleased to announce the immediate availability of Nexus Repository 3.6.0 OSS and Pro. A summary of the highlights in this release is shown below.

Please see JIRA for the complete list of changes.

Docker Anonymous Support

NEXUS-10813

This change makes it possible for anonymous users to be granted read-only (pull) access. It’s enabled by a new Docker repository connector option and realm. Anonymous read support can be deactivated by default and must be enabled on each Docker repository individually. Ultimately, this is useful as it allows users to consume and share Docker images with no credentials needed.

Goodbye JEXL, Hello CSEL

NEXUS-13942

We’ve discovered that Apache JEXL based content selectors aren’t fast enough for our upcoming tree view feature, which does many more evaluations than other browsing methods. To address this we’re introducing our own Content Selector Expression Language (CSEL) to support current features, such as Upgrading, and future improvements that rely on optimal performance.

Nexus Repository will automatically upgrade as many of your existing JEXL selectors to CSEL selectors as possible. Any remaining JEXL selectors will continue to function but with this new expression language in place, future releases of the repository manager will be more performant.

Provisioning API and Group Repositories

NEXUS-14038

Groups repositories created through the provisioning API will now preserve the order of their members. Previously, the initial ordering was set correctly, but jumbled on server restart.

For existing repositories affected by this, the workaround is to load the group repository in the UI, reorder the members as desired, and save.

Firewall and IQ Server

Firewall now requires the IQ Server connection capability to be configured and enabled. Previously, it would process transactions (e.g. audit) regardless, but a recent change now requires this capability.

Upgrading from 2.x

If you’re upgrading from Nexus Repository 2, you must first upgrade your installation to 2.14.5. See the upgrade compatibility matrix for more information.

Download it Now

To download Nexus Repository 3.6.0, visit the Sonatype OSS download site, or our download page.

The following two tabs change content below.

Michael Prescott

Michael Prescott is Product Owner/Nexus Repository Manager, where he helps to shovel coal as fast as he can into the fabulous engine that is the Nexus RM engineering team.

Related posts

One Comment;

  1. Michael Hoffmann said:

    Especially for things like YUM repos, but potentially others, how does Nexus deal with “seeding” proxy caches?

    In other words, what if I want to offer readily available and searchable mirrors of YUM repositories? What happens when I do a “yum update” from a client machine pointing to Nexus? What happens when I do “yum whatprovides /usr/bin/python” or such?

    Can I tell Nexus “you’re now proxy for repository [epel], mirror it now”. Similar to how I would go about with reposync.

    Even better, can I import existing YUM repos, so as not to recreate our already substantial mirrors? (goes for PyPi and NuGet, as well). This may sound ridiculous, but in Australia we’re still subject to quotas and speed shaping.

*

Top