JBoss Moves to Central
Sonatype is excited to announce that we’ve teamed up with Red Hat to add the popular JBoss Community project components to the Central Repository.
Many JBoss projects, including JGroups, Javaassist, Netty, Hibernate, HornetQ, RestEasy, jBPM and Drools are now included in the Central Repository with more expected to be added in coming months. You’ll be able to easily locate and use these projects in a single, standard location.
The Sonatype team worked closely with JBoss Community project teams to evaluate legacy repositories, cleanup metadata and coalesce disparate content into a single site. Providing transparent, streamlined access to important project artifacts in the Central Repository further accelerates the development process and enables the JBoss Community to more rapidly provide its open source technologies to users.
The Central Repository is the industry-leading source for open source Java components used by over 40,000 development organizations daily. Sonatype has been working to expand the number of components available in Central. By adding the JBoss projects and the Java.net projects announced last month, we expect the Central Repository to offer you access to more than 90 percent of all open source Java projects by the end of this year.
Read more in our press release.
JBoss Switches to Nexus Professional
Over the weekend, the JBoss repository team put the final pieces in place to complete the switch to Nexus Pro. We’ve been working with them since early this year to perform analysis and tool support for the conversion. Their team performed very diligent testing of the entire system prior to the conversion. Kudos to Paul for such an orderly and thorough process. The timing of the production switch is great because we are nearly done helping to clean up the Java.net repositories.
Historically the JBoss and Java.net repositories have been painful for Maven users. The reasons for this pain differed in each case, but overall these repositories have affected a large section of the community because of the popularity of the artifacts they contain.
The JBoss repository generally had decent metadata and release practices. The major concern in this repo was that the single repository contained artifacts in the following categories: 1) JBoss original artifacts 2) Copies of artifacts from other repositories 3) Artifacts with the same coordinates as artifacts in another repository, but that had been patched or otherwise altered
Ideally the repository should have contained only artifacts in category 1. Category 3 is what caused the most pain, because as soon as you pulled some artifacts from the JBoss repo, you potentially could get “polluted” with these altered artifacts.
Maven Archetypes and Nexus: "There is No Faster Way"
“Get Running on CDI & JSF2 in a Jiffy Using Maven Archetypes” – is a good illustration of how Maven and Nexus help make it easier for open source projects to distribute code and project templates to developers. (more…)
