+1 on having this in the Maven repos. >From what I recall, you don't actually push to the central repo--you get in contact with them, identify yourself as a project owner/committer, then set up some shared keys so they can log on to a server of yours to check for changes and upload them.
With the java.net repo you can do a push, and there are Ant/Maven scripts to help do that. You just need to contact them with a java.net id. However it works, would be nice to have these artifacts in the repos. Patrick On Wed, Aug 5, 2009 at 9:06 AM, Jeff Ramsdale<[email protected]> wrote: > Would others see a benefit to deploying the Apache River artifacts to the > central Maven repository upon a successful Hudson build (i.e. SNAPSHOTs)? > Even better, when AR2 is released? I'm sure the Maven Jini Plugin, Maven > Classdep Plugin and Rio (to pick several examples) could benefit from having > those managed by this community rather than independently. How difficult > would this be to add to the current release process? > -jeff >
