[jboss-jira] [JBoss JIRA] Commented: (JBBUILD-597) Synchronize JBoss artifacts from the JBoss repository to the Maven central repository

[ https://issues.jboss.org/browse/JBBUILD-597?page=com.atlassian.jira.plugi... ] Bob Fields commented on JBBUILD-597: ------------------------------------ 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/. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira