This blog has moved here

Deploying Maven artifacts using the java.net repository is always a challenge and most of the time the result is unpredictable...the good news is Sonatype's is opening it's Nexus OSS instance for all of the java.net project!

All the projects I'm involved that needs to deploy on java.net maven repository are daily failling (many many times) with the not so nice exception:

[HUDSON] Archiving <http://hudson.sfbay/job/Atmosphere/org.atmosphere.samples$atmosphere-simple-jersey/ws/target/atmosphere-simple-jersey-sources.jar> to /files/hudson/server/jobs/Atmosphere/modules/org.atmosphere.samples$atmosphere-simple-jersey/builds/2010-02-24_18-18-14/archive/org.atmosphere.samples/atmosphere-simple-jersey/0.6-SNAPSHOT/atmosphere-simple-jersey-sources.jar
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Error installing artifact's metadata: Error while deploying metadata: Connection failed: Unable to connect to https://svn.dev.java.net/svn/maven2-repository/trunk/repository/

svn: The specified baseline is not the latest baseline, so it may not be checked out.
svn: CHECKOUT of '/svn/maven2-repository/!svn/bln/2053093': 409 Conflict (https://svn.dev.java.net)
[INFO] ------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 22 minutes 9 seconds
[INFO] Finished at: Wed Feb 24 18:40:27 PST 2010
[INFO] Final Memory: 78M/168M
[INFO] ------------------------------------------------------------------------
Waiting for Hudson to finish collecting data\

This happens for project like Grizzly, Atmosphere and Jersey, making the deployment of SNAPSHOT and official release quite complicated. Project like GlassFish started using their own repository to workaround that issue. When I was at Sun we worked on tricks like committing the artifact manually using SSH (wow!), or use scripts that try over an over until it succeed (wow!). With Grizzly, it took sometimes 3 DAYS to deploy the official release. So I guess we can say the java.net repositoty is a little broken :-).

Now will it get fixed when java.net/kenai merge? We have to see...but Kenai doesn't have a Maven repository so I suspect the same one will be used, hence all the pain! But there is a good news! Sonatype is opening it's Nexus OSS instance to all java.net project (actually not only java.net...any OSS projects). You can read the official announcement here....the java.net migration day is targetted March 5! If you use Maven and deploy on java.net, I think that's a good opportunity to save pain and improve your release cycle!

This blog has moved here

It is always hard to write these type of posts. As of December 4th, I will no longer be with Sun Microsystems.

It all started from working on Java EE1.3 and a server called Tomcat. I was on Tomcat for a couple of years and then came with the idea of a NIO based HTTP Connector for Tomcat called ... Grizzly :-) Funny it never ended into Tomcat! Grizzly started with SJS AS 8.0 and slowly replaced the old Netscape C Runtime and Tomcat inside Sun's products (they are many many now :-)). I've then moved to a Project called Minnow, a components based server running on top of Grizzly and Maven 2. You start Grizzly and Grizzly was, at runtime, taking care of downloading/installing the artifacts needed to serve the request: Containers installed on the fly! The project got canned as soon as I've presented it internally ...I've always had trouble inside Sun with my projects :-) ... but it has opened the door to GlassFish v3 as the code got re-used to create the Grizzly based micro-kernel of the current GlassFish v3. Didn't wasted my time finally :-) During that time GlassFish moved from being a Zero to a Hero, and now it is just amazing to see where GlassFish is and the perception the community have of it. My fingers hurt when I look at the emails traffics we have generated on users@glassfish! Finally the "Comet things" surrounded me and at the end I've created the Atmosphere Framework, which is positively invading the planet those days :-).

I will really miss my team I've been working for the last 7 years.....Now the sad news: I will stop working on both GlassFish and Grizzly on December 4, letting something I've created growing by itself. But the Grizzly community is quite mature and I'm fully confident to see amazing release in the future! BTW, since I am privately getting up to 30 emails per weeks from early adopter or existing GlassFish users, please make sure you either ping Sun's support directly or use the Grizzly/GlassFish public mailing list to get the appropriate response starting now :-)

What about Atmosphere? This project is way too innovative to leave it and I will continue working on it or on something similar, depending on what Sun is up to :-).

Where do I go? I'm going to Ning.com. Don't worries I will continue polluting this blog and worse you can always follow me on Twitter!