's NexusMaven service is now available for projects. The new service will be replacing the Maven2-repositoryproject.'s Nexus Version is hosted at


If you're unfamiliar with the benefits of Maven repository managers, you'll find a good introduction in John Ferguson Smart's article, Maven Repository Managers for the Enterprise. John cites the following benefits as key reasons for using a Maven repository manager:

A correctly-configured repository manager can speed up your builds, save bandwidth, help you share artifacts within your organization, and give you better control as to what dependencies are used in your projects and where they are coming from. It can also play a key role in your development infrastructure, helping you set up a fully-blown automated build and deployment pipeline.

To learn about the main features of Nexus, visit Sonatype's Nexus page. The overview includes a link to an introductory video and also points you to the introductory chapter of the book, Repository Management with Nexus. The Sonatype Pro for Nexus page provides more links to references on what's included in the Nexus Professional edition (what we have on

A Maven Repository Usage Guide is available to help you get started with applying's Nexus Maven repository hosting service to your project. Sonatype created the Usage Guide, and they are actively involved in providing and managing's Nexus service. Using the service:

You can deploy snapshots, stage releases, and promote your releases so they will be synced to Maven Central. To assure the quality of artifacts in Maven Central, all new release versions must meet some quality requirements. Once you have new a release version deployed to Nexus repository, we will help you clean up old versions and sync them into central.

Migration from Maven 2

Now that Nexus is up and running,'s legacy Maven 2 repository serviceis scheduled for eventual deprecation. No deprecation date has yet been set. However, if you've been using the Maven 2 service, you'll want to migrate your project to Nexus sooner rather than later, to avoid any potential downtime or other issues. The starting point for migrating your project to the new Nexus Maven service is to create a JIRA ticket requesting that your project be migrated. Refer to Maven Repository Usage Guide for more information.

The GlassFish projects and several others have already been migrated to Nexus, so the process is already tested and well understood. Basically, the migration involves the following steps (after you've submitted your Jira request):

  • validate and repair (if necessary) the old Maven 2 artifacts;
  • move/copy the artifacts to the new repository;
  • configure access in Nexus to the new project; and
  • learn how to use the new repository.

Most of this is handled by Sonatype, which will work closely with each project team as their project is migrated.

The Sonatype Nexus Maven repository service is a major addition to the toolkit available to project owners, one that was long requested, and which turned out to be a long time in coming. It's great to have it up and running on the new! Weblogs

Since my last blog post, Fabrizio Giudici also published a blog post that just happens to be related to Maven 3, Happiness is...


Our current poll asks "Now that you're accustomed to it, what do you think of the new" Voting will close on Monday, June 6.


Our latest article is Data Analysis and Data Mining Using Java, Jython and jHepWork, by Sergei Chekanov and Alejandro D. P. de Astorza.

Java News

Here are the stories we've recently featured in our Java news section:


Our latest Spotlight is the announcement, JavaFX 2.0 Beta Now Available:

The much-anticipated JavaFX 2.0 beta release is now available for download - which means you can take advantage of all the new benefits that JavaFX 2.0 brings to the Java platform. This release is the latest development in Oracle