Sonatype Rescue Mission For Java.net Projects
Jason van Zyl has announced a Sonatype rescue mission on March 5th in response to what he refers to as “numerous problems with the Maven repositories on Java.net.”
In a blog post, Sonatype pinpoint the repository infrastructure at Java.net as the root of countless headaches for Java.net hosted projects. Zyl cites complains about mix-ups between both Maven 1 and Maven 2 repositories, and releases and snapshots, and a lack of javadocs, sources and signatures. The post also complains of poor project metadata, and sums up its list of Java.net-related problems by claiming Java.net demonstrates a “general inability……..to provide any coherent means of delivering valid repository content to the Maven community.” In the past, projects like GlassFish have used their own repositories to workaround Java.net’s difficulties with Maven.
But, Zyl is determined to put this right: “I figured instead of continuing to complain –and continuing to field the complaints of Maven users– I’m going to do something about it.” Hence, Juven Xu and Marvin Froeder from Sonatype will begin work on servicing all requests to migrate projects’ Maven Repository infrastructure from Java.net, to Sonatype’s Nexus OSS instance. Sonatype are dedicating an entire day – March 5th, 2010 – to helping Java.net projects make the transition. Although, Java.net projects will still be able to access Sonatype’s help after this date.
Creator of Project Grizzly, Atmosphere and contributor to GlassFish, Jean-Francois Arcand has already pledged his support to Sonatype’s rescue mission. In a blog post, he admitted that “deploying Maven artifacts using the java.net repository is always a challenge and most of the time the result is unpredictable” before enthusing that “the good news is that Sonatype is opening its Nexus OSS instance for all of the java.net project!”
Sonatype request that projects interested in making the switch, should first read the company’s guide for OSS Repository Hosting.