0 Replies Latest reply on Apr 23, 2010 2:23 PM by rhauch

    JBoss Maven Repository changes

    rhauch

      JBoss.org recently launched a new Maven Repository implementation [1] to house all JBoss-related artifacts. This new repository is much more powerful and capable than our old SVN-based one and includes a nice browse/search web front-end [2], but it may require a small change to your Maven settings.

       

      Those of you using ModeShape in your own applications or projects likely have Maven settings that involve multiple Maven repositories, including the old JBoss Maven 2 repository [3]. The only change you'll want to make is to use the new JBoss repository in addition to your other Maven repositories [4]. Then, when you build your application with Maven, JBoss-related artifacts will be downloaded from the JBoss repository while other libraries (including those we depend upon) are downloaded from the other Maven repositories.

       

      Those of you that are contributors to ModeShape (or other projects hosted at JBoss.org) will want to use a different configuration [5]. With this configuration, your Maven builds download all artifacts through the JBoss Maven repository, which proxies other 3rd party repositories and maintains a local cache of all these artifacts. This speeds up the artifact resolution process of your builds, but also ensures that these artifacts are always available to JBoss to build our projects/products (even should other 3rd party repositories disappear).

       

      As usual, if you have any questions, please ask.

       

       

      [1] http://community.jboss.org/en/build/blog/2010/04/20/announcement--new-maven-repository-infrastructure

      [2] https://repository.jboss.org/nexus

      [3] http://repository.jboss.org/maven2

      [4] http://community.jboss.org/wiki/MavenGettingStarted-Users

      [5] http://community.jboss.org/wiki/MavenGettingStarted-Developers