JBoss Build System
  1. JBoss Build System
  2. JBBUILD-597

Synchronize JBoss artifacts from the JBoss repository to the Maven central repository

    Details

    • Similar Issues:
      Show 10 results 

      Description

      Synchronize JBoss artifacts from the JBoss repository to the Maven central repository

        Activity

        Hide
        Emmanuel Bernard
        added a comment -

        There has been numerous requests over time for that from different users and different projects.
        This issue is here to gather needs and progress.

        Show
        Emmanuel Bernard
        added a comment - There has been numerous requests over time for that from different users and different projects. This issue is here to gather needs and progress.
        Hide
        Paul Gier
        added a comment -

        I talked with one of the maintainers of central (Brian from Sonatype) about doing this, and he is open to the idea. The first thing we need to do is allow rsync from our repository. In the past, operations has not been very open to allowing this. I explained the benefits related to reduced load on our server and they are more open to the idea now.

        Once rsync is set up, the plan will be to sync specific groupIds from our repository. The artifacts going to central will have to be validated first (to check for invalid POMs, incomplete dependency tree, etc). So longer term we should be able to set up the same validation rules in our repository that are used for oss.sonatype.org and for central, and then eventually sync everything or at least the majority of our stuff.

        Show
        Paul Gier
        added a comment - I talked with one of the maintainers of central (Brian from Sonatype) about doing this, and he is open to the idea. The first thing we need to do is allow rsync from our repository. In the past, operations has not been very open to allowing this. I explained the benefits related to reduced load on our server and they are more open to the idea now. Once rsync is set up, the plan will be to sync specific groupIds from our repository. The artifacts going to central will have to be validated first (to check for invalid POMs, incomplete dependency tree, etc). So longer term we should be able to set up the same validation rules in our repository that are used for oss.sonatype.org and for central, and then eventually sync everything or at least the majority of our stuff.
        Hide
        Bob Fields
        added a comment -

        The main benefit is wider use of the JBoss and Hibernate artifacts, because it is easier to configure maven (no additional repositories) and because projects outside JBoss which depend on the JBoss runtime or Hibernate libraries are now available automatically through the maven Central repository. In our case (www.andromda.org) we have current SNAPSHOT dependencies on JBoss 5.1 and Hibernate 3.5 and cannot create a release version of the project because those dependencies are not in Maven Central, unless we want to drop back to JBoss 4.2 and Hibernate 3.2.

        Rules for adding projects to maven central are at https://docs.sonatype.org/display/Repository/Central+Sync+Requirements. Specifically,

        • Blind rsync transfers of random repositories are no longer being added and will be phased out over time
        • All artifacts must be properly signed with GPG signatures that are publicly verifiable
        • sources and javadocs must be included
        • scm urls must be included
        • No external repository definitions
          Includes comments on why putting repositories in your release artifact poms is a bad idea, and why they are being phased out of maven central. Since you're already on Nexus, enforcing those requirements within JBoss would be easy to implement, after cleaning up the current releases that are already there. The solution for rsync is to become a feeder repository to the Sonatype Nexus staging suite, as described in http://www.sonatype.com/people/2010/01/nexus-oss-ecosystem/.
        Show
        Bob Fields
        added a comment - The main benefit is wider use of the JBoss and Hibernate artifacts, because it is easier to configure maven (no additional repositories) and because projects outside JBoss which depend on the JBoss runtime or Hibernate libraries are now available automatically through the maven Central repository. In our case (www.andromda.org) we have current SNAPSHOT dependencies on JBoss 5.1 and Hibernate 3.5 and cannot create a release version of the project because those dependencies are not in Maven Central, unless we want to drop back to JBoss 4.2 and Hibernate 3.2. Rules for adding projects to maven central are at https://docs.sonatype.org/display/Repository/Central+Sync+Requirements . Specifically, Blind rsync transfers of random repositories are no longer being added and will be phased out over time All artifacts must be properly signed with GPG signatures that are publicly verifiable sources and javadocs must be included scm urls must be included No external repository definitions Includes comments on why putting repositories in your release artifact poms is a bad idea, and why they are being phased out of maven central. Since you're already on Nexus, enforcing those requirements within JBoss would be easy to implement, after cleaning up the current releases that are already there. The solution for rsync is to become a feeder repository to the Sonatype Nexus staging suite, as described in http://www.sonatype.com/people/2010/01/nexus-oss-ecosystem/ .
        Hide
        Paul Gier
        added a comment -

        We're currently working with Sonatype to set up automatic rsync to central. We'll be starting with a few smaller directories (groupIds) and gradually including more as we go along. I'll post to the build blog when there is more information to share.

        Show
        Paul Gier
        added a comment - We're currently working with Sonatype to set up automatic rsync to central. We'll be starting with a few smaller directories (groupIds) and gradually including more as we go along. I'll post to the build blog when there is more information to share.
        Hide
        Paul Gier
        added a comment -

        The rsync is now active for certain groupIds. I posted some additional information on the jboss build blog.
        http://community.jboss.org/en/build/blog/2011/05/24/rsync-jbossorg-to-maven-central

        Show
        Paul Gier
        added a comment - The rsync is now active for certain groupIds. I posted some additional information on the jboss build blog. http://community.jboss.org/en/build/blog/2011/05/24/rsync-jbossorg-to-maven-central
        Hide
        Paul Gier
        added a comment -

        The sync is now active, and the rollout for the remaining groupIds will be tracked in the wiki:
        http://community.jboss.org/wiki/MavenRepositoryCentralSynchronization

        Show
        Paul Gier
        added a comment - The sync is now active, and the rollout for the remaining groupIds will be tracked in the wiki: http://community.jboss.org/wiki/MavenRepositoryCentralSynchronization

          People

          • Assignee:
            Paul Gier
            Reporter:
            Emmanuel Bernard
          • Votes:
            14 Vote for this issue
            Watchers:
            15 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: