Kohsuke Kawaguchi's Blog

java.net site-wide maven repository

Since I wrote the last blog entry about the maven java.net plugin, Ross Bamford joined the development, and we've been working on the Maven repository for all java.net projects.

The idea is to have a single Maven repository where all java.net projects can publish their artifacts. This has two benefits; the first is that it becomes easier for other projects to depend on java.net projects, because all the artifacts are available from a single repository. The second is that you can host your artifacts in a publicly visible server without the overhead of posting artifacts to ibiblio.

I mostly worked on the server side, where the daemon collects all the artifacts from all the participating projects and publish them in once place (see this.) Ross implemented a series of javanet:deploy-XXX targets to the maven java.net plugin, which pushes the artifacts into this repository.

We still need to polish up the documentation and etc, but it's already good enough to call it beta-quality. You can try it for your project by following these instruction. We are interested in getting feedback before we finalize this service, so please let us know what you think!

Comments

• Doesn't one usually use the maven jar:install task to put, for example, a jar in the repository? Perhaps the javanet: goal hierarchy could model this a little better--there are already enough things to remember about maven. Thanks for the effort of putting this together!

  Best,
  Laird

  Posted by: ljnelson on September 24, 2005 at 06:41 AM

• Thank you for your comment. I think Ross indeed wanted to do it that way initially, but he eventually he decided there wasn't enough hook to do it.
  Do you know how it can be done? Would you be willing to help us :-)?

  Posted by: kohsuke on September 24, 2005 at 10:14 AM

• Actually, jar:install handles copying artifacts to your local repository - if you have access to a live repository (maybe accessed by SSH or FTP) you'd use jar:deploy (or the old jar:deploy-snapshot) goal to deploy your artifact. This is mirrored also by war:deploy, dist:deploy, plugin:deploy and so on.

  As Koshuke mentions, we originally wanted to go the way you suggest (though using jar:deploy rather than install), but it just wasn't meant to be...

  Thanks for your feedback!
  

  Posted by: roscopeco on September 26, 2005 at 05:20 AM

This work is licensed under a Creative Commons License.