Eduardo Pelegri-Llopart wrote: Is there a policy on what "relatives" we'd be willing to host? The maven-repository home page implies any java.net hosted project could use this ... betcha lots of java.net project owners do not know that.

My gut says Maven-oriented developers will prefer fine grained dependencies on the point APIs, rather than a global dependency on javaee.jar (although people targeting Glassfish as a platform might like the combined one as well, for convenience in building POMs).

One technical aspect is that the infrastructure for this repository is based on https: rather than http:.

In addition to making transactions slower than they would otherwise be, Maven seems to have problems accessing https repositories through a proxy (such as from behind the Sun firewall). Synchronizing to ibiblio would deal with this, as well as reduce configuration setup of having to specify the java.net repository.

A second technical aspect that doesn't need to be addressed urgently, but should be considered for the future, is that we're using the legacy (Maven1) organizational format. The Maven2 organization seems more scalable.

I'm something of a Maven newbie (Shale's build is in the process of being switched over to Maven2), but I'm willing to do whatever I can to help.