The latest edition of Repository Management with Nexus, Edition 2.1, has been released. This edition includes new content about Nexus 1.5.0 Open Source and Enterprise LDAP. Edition 2.1 also contains almost 100 corrections which were driven by the community.
Devnexus 2010 is the annual Professional Developer Conference, and is being held in Atlanta on March 8 and 9. Sonatype’s Jason van Zyl will be in Atlanta on March 8 to give a presentation on Maven 3 and Next Generation Development Infrastructure. The presentation will cover the future of Maven, Maven 3, the release of m2eclipse 1.0, and the move towards a standardized development stack that includes tools like Maven, Hudson, m2eclipse, and Nexus.
This discussion will focus not only on the tools individually, but how they can work together to create a best practices approach to building and delivering your software in your organization.
For more information on Devnexus 2010 visit the conference website. Devnexus 2010 is sponsored by the Atlanta Java User Group.
Parleys.com has just published my “Maven 3: Reloaded” presentation from Devoxx ’09. In this presentation, I put our current focus on Maven 3 in context and talk about some of the upcoming technologies like Polyglot Maven and Maven Shell. In this video you’ll see me demonstrate POM translation from XML to Groovy, discuss the ways in which Maven 3 changes allow m2eclipse to embed Maven, and some of the work we’ve done in Tycho to provide a path for OSGi developers.
You watch this embedded video, or watch the presentation over on the Parleys.com site.
Note: To switch between the slides and the video of me talking, click on the smaller video in the upper right-hand of this video embed.
Good news travels fast, and word about our Java.net Maven Repository Rescue Mission is getting a positive response.
I guess we can say the java.net repository is a little broken…But there is a good news! Sonatype is opening it’s Nexus OSS instance to all java.net projects.
This blog entry details a few examples of the headaches that the Java.net repository has caused. You can read the full blog entry here. As promised, on March 5th we will start servicing all requests to switch Java.net projects over from their Maven Repository infrastructure to our Nexus OSS Instance.
If you use Maven and deploy on java.net, I think that’s a good opportunity to save pain and improve your release cycle!
There are numerous problems with the Maven repositories on Java.net, and individual projects are being penalized for poor development infrastructure at Java.net. We hear no end of complaints about the poor quality of Maven Repositories at Java.net: mixing of Maven 1 and Maven 2 repositories, the mixing of releases and snapshots, lack of javadocs, sources, signatures, bad project metadata, and general inability of Java.net to provide any coherent means of delivering valid repository content to the Maven community.
This is not a problem with any particular project at Java.net, it’s the infrastructure provided by Java.net that isn’t up to par. You need to provide a decent Maven repository infrastructure for projects to deploy their content to, and you need to provide instructions about best practices on how accomplish this properly. Java.net has done neither, so I figured instead of continuing to complain –and continuing to field the complaints of Maven users– I’m going to do something about it.
On March 5th, 2010 Juven Xu and Marvin Froeder from Sonatype will start servicing any and all requests from Java.net projects to migrate their Maven Repository infrastructure over to our hosted Nexus OSS instance. We will, of course, continue to service requests after March 5th, but March 5th will be set aside to specifically help Java.net projects get switched over and tested.
We generally ask that projects interested in our OSS hosting service familiarize themselves with our guide for OSS Repository Hosting. If you follow the guide and make your request we will process the requests on a first come, first serve basis on March 5th. We’ve helped close to 100 projects now and we’d love to help the projects at Java.net!