commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From sebb <>
Subject Re: Nexus vs rsync-repository releases
Date Tue, 02 Aug 2011 14:52:36 GMT
On 2 August 2011 15:29, Mark Thomas <> wrote:
> On 02/08/2011 15:23, Emmanuel Bourg wrote:
>> Are we still going to deploy Maven artifacts by SCPing to
>> m2-ibiblio-rsync-repository on
>> I've been discussing the permissions issue for the old groupIds on Nexus
>> with the Infra team (i.e components using the old groupId
>> commons-<componentname> need a specific configuration on the snapshot
>> and release repositories).
>> Brian Demers kindly proposed to allow the deployment of all commons-*
>> groups on Nexus, but it would require to block the deployment through
>> to avoid metadata conflicts.
>> Do we all agree on using exclusively Nexus for our releases?
> What benefits do we get by using Nexus and what extra hoops do we have
> to jump through to get them compared to just using scp?

The benefits are:
* metadata is automatically updated
* intercepts all uploads, so cannot accidentally deploy to live repo
* automatically checks that signing keys are publicly available
* ensures that the artifacts voted on are the ones actually deployed

Nexus is automatically used if the gid is o.a.commons.

One just has to use "mvn deploy" and the artifacts will be uploaded to
the staging area.

The extra steps that have to be done are:

1) Close the staging repo once all the artifacts have been uploaded.
This makes the staging area visible for release votes.

2a) Publish the staging repo once the release vote has passed. This
allows the artifacts to propagate to Maven Central.


2b) Drop the staged artifacts, and re-roll the release.

> Mark
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message