I staged the 0.10 maven artifacts last night. Should anyone else wish to test them before they get promoted or dropped, they are now available here:
https://repository.apache.org/content/repositories/orgapacheqpid-109/ Robbie On 19 April 2011 13:09, Robbie Gemmell <[email protected]> wrote: > Moving this off the 0.10 vote thread as I actually planned to last time :) > > The process for releasing these is detailed at > http://www.apache.org/dev/publishing-maven-artifacts.html as previously > mentioned, and involves them being published to the ASF's Nexus instance at > https://repository.apache.org , from where they will be synced to the > central Maven repo. Once the artifacts are initially uploaded they are > placed into a Staging repo, which can then either be closed to prepare it > for release or dropped if something goes wrong with the upload. Once the > repo is closed, the staged artifacts can then be tested and voted on, and > then either dropped or promoted to the Releases repo once the vote > concludes. > > I had previously investigated using Ant+Ivy in the way detailed at the dev > page above, and so put together a task to publish our current maven release > artifacts (found at > http://people.apache.org/~astitcher/dist/qpid-0.10/maven/ ) to a Nexus > Community Edition instance I set up locally. I also requested infra to > enable our access to the ASF's Nexus Professional instance, which has now > been completed. I have just tested that the task is able to successfully > upload to the ASF's instance, and so have committed the work against > https://issues.apache.org/jira/browse/QPID-3213. The task is currently > standalone from the rest of the build, and instructions for using it are on > the JIRA (probably best added to a nice release process page at some > point..). > > I have dropped the staged artifacts I created when doing the above, because > the staging repos are named based partially on an IP for the uploader and I > am currently stuck behind a load balancing proxy server which resulted in 3 > staging repos being created instead of just 1 for all the artifacts. I am > happy to either perform the staging myself when I am at home later, or for > Andrew Stitcher to do so in keeping with his publishing of the other > artifacts. > > Robbie > > On 15 April 2011 14:29, Robbie Gemmell <[email protected]> wrote: > >> The instructions cover an upload-only use of Ivy, which is something I >> have been investigating and plan to put in place so we can publish the >> artifacts to Nexus. >> >> Robbie >> >> >> On 15 April 2011 13:57, Emmanuel Bourg <[email protected]> wrote: >> >>> Le 15/04/2011 13:50, Andrew Kennedy a écrit : >>> >>> >>> One thing I'm not clear on. Since the genpom stuff has been fixed (See >>>> QPID-1916 - thx, Robbie and Emmanuel) are we going to disseminate >>>> Maven artifacts as part of 0.10 now? That would definitely be nice to >>>> have. I believe we can upload to >>>> https://repository.apache.org/content/repositories/releases/ once we >>>> have the approved release artifacts, but I'm not sure of the correct >>>> process. I can find out if nobody else knows? >>>> >>> >>> There are some instructions on the Apache site: >>> >>> http://www.apache.org/dev/publishing-maven-artifacts.html >>> >>> >>> These instructions are for a Maven or an Ant+Ivy setup. For Qpid we used >>> an Ant+Maven Task setup, so I don't really know how to publish to Nexus with >>> our build. >>> >>> >>> Emmanuel Bourg >>> >>> >> >
