If you are a software developer, you most likely rely on a Maven Repository Manager to acquire, manage, and report on open source software artifacts — the building blocks of application development. Nexus is the industry-leading Repository Manager, and the recent release of Nexus 1.6 brings many exciting upgrades to both Nexus and Nexus Professional. But how do you decide what version of Nexus is best for you?
There are a few things to consider. Below is just a few differences to keep in mind and help you make the best decision.
In Nexus 1.6, we reintroduced a useful little feature that had been available in early 1.0 betas: The ability to have Nexus auto block proxies that are unreachable. What’s improved in this version is the ability to control this feature and the fact that it will auto unblock the repo once it becomes reachable again.
Whenever an artifact is downloaded from a proxy repository, it is automatically cached locally and used to serve subsequent requests. Nexus will continue to serve the artifact until it expires based on the configuration (release artifact typically never expire).
When new artifacts are being requested that Nexus has never seen before, it will look in the proxies to locate it (this behavior can be optimized with routing rules). If the remote request times out, Nexus by default will check two more times before giving up. This is usually enough to handle transient network glitches. If however, the repository is down for an extended period of time, all these retries can back up the connections and slow down over all performance. This is where the auto block comes in.
Sonatype is happy to announce the availability of Nexus 1.6. We’ve cut a new release for both Nexus Open Source and Nexus Professional. This post walks through the changes introduced to both Nexus Open Source and Nexus Professional. Nexus Open Source now supports auto block/unblock for remote repositories which may become unavailable, and Nexus Professional adds some new configuration fields for the Staging Suite. In addition to these new features, Nexus has now completed the transition to Guice, and we are providing 100% documentation coverage of the Nexus REST API. Continue reading