Updated Maven infrastructure @ maven.java.net

Sonatype's Nexus Maven Repository Manager is now running at java.net. This will offer the numerous java.net Maven users the typical repository manager benefits but maybe most importantly an overall cleanup.

ALT_DESCR

Over on the java.net editor's blog, Kevin has more details on what this means for users and contributors to java.net-hosted projects while this document lays out the role of the various repositories, the relationship to Maven central as well as more general prerequisites and requirements for publishing artifacts.

GlassFish artifacts have started being deployed to this new Maven repo (maven.java.net) and we expect little to no impact for GlassFish users. The final (stable) bits for Embedded GlassFish should be deployed to Maven central. If you're new to Maven, you may want to check out the replay of our recent Maven webinar.

The Nexus version deployed is the latest available (1.9.1.1) and most of the work was actually carried out by Sonatype.

Comments:

While better Maven support for Glassfish certainly is good news, this announcement is a little confusing: Are you talking about great things to come or changes effective as of now? I can't see any org.glassfish.extras artifacts in https://maven.java.net/content/groups/public/, so it seems the repository for Embedded Glassfish still is http://download.java.net/maven/glassfish. Is this going to change? If so, then there _will_ be an impact for Embedded Glassfish users working with Maven. You also mention that "stable bits should be deployed to Maven central" - I absolutely agree. Does that mean that Embedded Glassfish or even all Glassfish-related artifacts will be available from Maven central in the near future? Regrettably, there has been a tendency for open source communities to set up their own Maven repositories instead of pushing things to Maven central, which forces users to manage ever growing lists of Maven repositories or to set up their own Nexus instance. PS: This comment looks garbled because the blog engine does not recognize double linefeeds as paragraphs, which is rather annoying...

Posted by Harald Wellmann on June 01, 2011 at 02:46 AM PDT #

Hi Herald, You will start seeing org.glassfish.* artifacts in the maven.java.net repository soon. Once that happens, you will not see new versions of Embedded GlassFish artifacts deployed to http://download.java.net/maven/glassfish. There will be no impact to Embedded GlassFish users since the stable versions will be deployed to Maven central. When the artifacts are available in Maven central, Embedded GlassFish users will not need to specify the "repository" element in pom files. If users are referencing the GlassFish Nexus server at http://maven.glassfish.org/content/groups/glassfish/, there will be no changes for them either. The plan is that final Embedded GlassFish and GlassFish-related artifacts will be sync'd in Maven central. However, keep in mind this will not happen right away since there are rules that we need to follow when syncing artifacts to Maven central and we are in the process of cleaning up download.java.net/maven artifacts. Hope I answered your questions. Jane

Posted by Jane Young on June 01, 2011 at 08:02 PM PDT #

Thanks, Jane, that makes it clearer!

Posted by Harald Wellmann on June 02, 2011 at 03:55 AM PDT #

Post a Comment:
Comments are closed for this entry.