The team is happy to announce a new Maven repository configuration.  Starting April 19, 2010, will be using the Nexus repository manager to provide a more robust and fully featured set of Maven repositories.  The goal is to make it easier for developers to release and manage project artifacts, and easier for the JBoss users to locate and use the dependencies necessary for their builds.




The old Maven repository consisted of a single directory structure containing all JBoss project dependencies.  This caused problems for many users because there was duplication between the JBoss repository and other Maven repositories (such as the Maven central repository).  The new JBoss system will provide a set of more focused repositories that can be used separately or grouped together into a single repository view.  Detailed information about the organization of the new repositories can be found in the JBoss wiki ( Maven Repository Organization )



The old repository URL ( ) will continue to be available in a read-only mode with the existing repository content.  This means that you don't need to switch to the new repository immediately, but all new releases should be deployed to the new system, so you will need to gradually migrate to the new repositories.  The next sections provide important information to be aware of before you start using the new repository.


Before Getting Started


There are a few things you should be aware of before you switch to the new repository URLs.


  1. Deprecated Repository - In an effort to clean up the JBoss repository, many artifacts have been moved to a "deprecated" repository.  This repository will not automatically be visible to your builds when using the new repository group URLs.  This means that if your build currently uses one or more deprecated artifacts, the short term solution is to add extra configuration to your Maven settings.  Specific configuration information is available in the getting started pages.  The long term solution is to update your project dependencies to use artifacts from one of the release repositories.
  2. Repository Performance - The new repository is more complex and will initially be significantly slower when downloading dependencies.  This will improve over time as the proxy repositories are populated, and we will continue to work to improve any additional repository performance problems.



Getting Started for JBoss Users

The new repository provides a search interface for easily locating the files you need.  It also provides more flexibility to download only the artifacts that you need.  Instead of a single large repository containing a mix of JBoss and thirdparty artifacts, there will now be several smaller repositories which allow you to choose only JBoss project artifacts, or a larger combined set of artifacts.


The new repository interface is available at


A complete guide for configuring your Maven builds is now available in the wiki Maven Getting Started - Users


Getting Started for JBoss Developers


Note: the developer repositories will be available soon after comes back on line.


The new repository provides several new features for JBoss developers:

  • Releases will be automatically staged for testing and review so you won't have to worry about accidentally deploying a broken release
  • Deployment to any of the repositories will now use a simple http URL instead of multiple confusing options for deployment
  • Deployments will update the repository immediately, so you won't have to wait for the repository to sync before seeing your release.
  • The combined contents of JBoss repository artifacts and thirdparty repositories will be available through a single URL, or through separate URLs depending on your choice of configuration.
  • The repository will automatically save any artifacts used from thirdparty repositories, so it will no longer be necessary to manually copy dependencies from thirdparty repositories.


A complete guide to configuring your environment is now available in the wiki Maven Getting Started - Developers




If you can't find the answer to your question on the wiki or you find problems with the repository, please communicate these issues through the JBBUILD Jira Project or through the build system forum.