Ah yes - I like the Nexus UI, but I haven't used these features yet. I need to crack open the Nexus documentation to find out how to do this.
Thanks again, Les On Tue, Feb 9, 2010 at 10:49 AM, Brian Demers <[email protected]> wrote: > Hey Les, > > On Tue, Feb 9, 2010 at 10:32 AM, Les Hazlewood <[email protected]>wrote: > >> Hi Brian, >> >> > To get everything setup for a staging repository >> > Create a sub task under: >> https://issues.apache.org/jira/browse/INFRA-1896 >> >> Done: >> >> https://issues.apache.org/jira/browse/INFRA-2488 >> >> > After the deploy you need to close the staging repo, and promote it >> >> What do you mean by close the staging repo? Just ensure that the team >> does not deploy to staging to prevent overwrites? >> > > A single maven deploy is a bunch of stateless deploys so there is no way to > know when maven is done deploying all the artifacts. So after you do a > deploy you need to tell Nexus you are finished. This puts the repository in > a read-only mode > > You could do this all from a maven plugin (but personally I like the UI for > this): > http://plugins.sonatype.org/nexus-maven-plugin/usage-staging.html > > >> >> Also, once the artifacts are in staging, how is promotion done in >> Nexus? I mean, let's say that the community votes to approve the >> release. How do you propagate those voted-upon artifacts from staging >> to the release repo? >> > > The actual promoting is also just a couple clicks (or the plugin listed > above) > Upon promotion all the artifacts are moved into the release repository. (and > corresponding metadata is merged i.e. maven-metadata.xml) > > > >> >> Thanks for the pointers! >> >> - Les >> >
