commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From sebb <>
Subject Re: [DAEMON] Tagging 1.0.6
Date Wed, 08 Jun 2011 00:40:20 GMT
On 7 June 2011 18:37, Mladen Turk <> wrote:
> On 06/07/2011 12:28 PM, sebb wrote:
>>> Q: I saw some projects are using svn for releases instead
>>> copying the artifacts trough the ftp. Are using this as well
>>> or the [1] is still valid?
>> AFAIK, that has to be set up through infrastructure first.
> Yep that was my understanding as well.
> Seems like easier then manually copying the files trough scp/ftp
> so might be something to consider as Commons wide.


How does it work for release votes?
Is there a staging area?
Or is it only used after the vote, at the release stage?

>> [1] does not cover components using Nexus, which includes Daemon.
>> In which case "mvn deploy" will copy the artifacts (Maven and
>> otherwise) to the staging repo.
>> See [2] and [3] for further info.
> I had problems earlier when trying to deploy the artifacts to maven.

I think that was before Nexus; also Commons Parent has been improved since then.

> Will you (or someone else) help me with that once we have
> the 1.0.6 voted?

I'm happy to help, but the deployment needs to be done before the
vote, as the Maven artifacts need to be included in the vote.

I'll try a SNAPSHOT deploy shortly and see if it works OK for the Java code.

Probably best if you sign the Maven code as well, but that should just
be a question of running the same command as I have.

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

View raw message