The Nexus 1.7.2 release offers an improved search interface making it even easier to locate the libraries and artifacts you need in Nexus.  Sonatype has published a version of Nexus 1.7.2 on http://repository.sonatype.org which contains some dramatic improvements to the search interface.   Download the new Nexus Open Source or Nexus Professional release and start searching for artifacts.

What is new in the Nexus 1.7.2 search interface?

• Search results now link directly to the latest version of a matching artifact.
• Selecting a search result immediately displays information about the matching artifact.  You can browse artifact information from the search interface.
• (Nexus Professional) Archive browsing and artifact metadata are available from the search interface.
• Matching artifacts of different types (pom, jar, war, zip, etc.) can be downloaded from the search results page.

This release takes the effort out of searching for artifacts in Nexus.  Here are some sceenshots of the new interface now available on http://repository.sonatype.org and soon to be available in the 1.7.2 release of Nexus Open Source and Nexus Professional.

Read more…

Nexus, Sonatype Nexus, nexus pro

With the 1.7.1 release Nexus Professional now supports multi-level staging and build promotion.   With our existing staging plugin, you can release build artifacts to a temporary staging repository to allow for testing and certification before making a final decision to release artifacts to a hosted repository.   With multi-level staging, you can add additional steps to your release process.   If you need multiple levels of testing or validation, you can now define both staging profiles and “build promotion” profiles.

When you stage an artifact in Nexus Professional, Nexus creates a temporary staging repository and exposes staged artifacts in a repository group.   When you promote a staging repository with a build promotion profile, you can configure Nexus to add promoted artifacts to additional repository groups.

Read more…

Nexus, Sonatype multi-level staging, Nexus, nexus pro, release, staging

Sonatype is happy to announce the availability of Nexus 1.7. We’ve cut a new release for both Nexus Open Source and Nexus Professional. This post walks through the changes introduced to Nexus Open Source.  Read more…

Sonatype Nexus, nexus open source, nexus professional, repository, Sonatype

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.

Read more…

Nexus Nexus, nexus 1.6, repository manager

Over the weekend, the JBoss repository team put the final pieces in place to complete the switch to Nexus Pro. We’ve been working with them since early this year to perform analysis and tool support for the conversion. Their team performed very diligent testing of the entire system prior to the conversion. Kudos to Paul for such an orderly and thorough process. The timing of the production switch is great because we are nearly done helping to clean up the Java.net repositories.

Historically the JBoss and Java.net repositories have been painful for Maven users. The reasons for this pain differed in each case, but overall these repositories have affected a large section of the community because of the popularity of the artifacts they contain.

The JBoss repository generally had decent metadata and release practices.  The major concern in this repo was that the single repository contained artifacts in the following categories: 1) JBoss original artifacts 2) Copies of artifacts from other repositories 3) Artifacts with the same coordinates as artifacts in another repository, but that had been patched or otherwise altered

Ideally the repository should have contained only artifacts in category 1. Category 3 is what caused the most pain, because as soon as you pulled some artifacts from the JBoss repo, you potentially could get “polluted” with these altered artifacts.

Read more…

Nexus jboss, nexus professional, repository manager, Sonatype