commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From sebb <>
Subject Re: [ALL] Remove some artefacts from Nexus? (Was: [VOTE][RC1] Release ...)
Date Fri, 11 Jan 2013 11:42:56 GMT
On 11 January 2013 10:57, Gilles Sadowski <> wrote:
> Hi.
>> [...]
>> btw. I found something is missing in your release guide on the wiki
>> (from the UsingNexus page):
> I'm not maintaining the page on the Wiki (I'll remove it). The
> "authoritative" source is in the "doc/release" directory of the CM's trunk.
>> Nexus release
>>   * remove commons-<component>-<version>-bin.* and
>>     commons-<component>-<version>-src.* from nexus staging area
> Can someone confirm this? In the affirmative, why are these uploaded to the
> server in the first place?

Because that is where Maven deploys them.

AFAIK Maven does not currently support independent deployment of the
source and binary archives.
They are either excluded from deployment, or they are uploaded to the
repo with the Maven jars.

We then vote on the staging repo which contains both Maven and dist/
release archives.
On successful vote, the dist/ (bin/src) archives are copied to dist/.
They are then deleted from Nexus so they don't end up duplicated in
the main Maven repo, but AIUI that step can be omitted.

>>   * Promote
> This is point 13 of the "recipe".
>> The removal of the bin and src artifacts should be done, otherwise they
>> are pushed to the maven repo. A quick check shows that many commons
>> releases have them included on maven, which just bloats their repo imho.
> Let's see if there is another reason... ;-)
> Regards,
> Gilles
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

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

View raw message