OK, looks like I went into a bit of a dead-end with all that Keys
stuff. Obviously i'm gonna need to do that for the proper release, but
that can come later.
I'll just do a mvn deploy, then, and see what happens.
Thanks.
Dan
On 30/01/2011 17:26, Benson Margulies wrote:
then Mark's got it. you just say 'mvn deploy'. It would be typical to
have a daily hudson job to do so.
It is not typical to bother to put PGP signatures on snapshots.
Snapshots are *****NOT RELEASES OF THE APACHE SOFTWARE FOUNDATION****.
Which means that the whole process is quite relaxed.
On Sun, Jan 30, 2011 at 11:55 AM, Dan Haywood<[email protected]> wrote:
@Benson,
Yes, we're on v8, see [1].
@Mark/anyone,
Is any sort of vote or check needed to make sure we've got everything in
order before I run the deploy?
@anyone,
What do I need to do in terms of PGP keys? I've documented what I've done
so far on our wiki [2]; basically:
- generated a public/private key for myself, using gpg --gen-key
- exported my public key, using gpg -a --export [keyId]> filename
- tried to update copied public key into [3]; however, I don't seem to have
commit privileges... who grants these?
Also, am I right in thinking that - because all releases (including
snapshots) are signed against a particular individual's PGP key, that it
isn't possible to automate the deployment of snapshots from Hudson?
Thanks,
Dan
[1] http://svn.apache.org/viewvc/incubator/isis/trunk/pom.xml?view=log
[2] https://cwiki.apache.org/confluence/display/ISIS/GeneratingPgpKeys
[3] https://svn.apache.org/repos/asf/maven/project/KEYS
On 30/01/2011 15:52, Benson Margulies wrote:
Are you using the ASF parent POM?
On Sun, Jan 30, 2011 at 10:38 AM, Mark Struberg<[email protected]> wrote:
usually a mvn clean install deploy will do fine.
Depending of whether you have setup your settings.xml correctly or not,
you might also need to add -Dusername=xxx and -Dpassword=yyy
LieGrue,
strub
--- On Sun, 1/30/11, Dan Haywood<[email protected]> wrote:
From: Dan Haywood<[email protected]>
Subject: Help - publishing snapshots...
To: [email protected]
Date: Sunday, January 30, 2011, 12:22 PM
Hi mentors,
Since - due to collective pressure of work - we're not
going to get a 0.1 release out for a while, I thought we
ought to at least get some snapshots out at least, ideally
as an automated job from our Hudson CI.
I've raised a JIRA on infra so we can publish to the nexus
repo [1]. This has now been actioned and closed.
Looking at the instructions [2] that were attached to the
comment that closed that JIRA, it looks somewhat like
publishing a snapshot isn't something that's fully
automated; rather it's a half-way step to publishing out a
full release.
So two questions:
- I'm a bit nervous of doing the wrong thing, with respect
to licenses/notices files missing etc. Is there
anything I need to do specifically here?
- on the instructions in [2], I can't quite see why the
release dryRun is required if all I want to do is to publish
a snapshot. Can I just do a "mvn deploy:deploy" ?
Cheers
Dan
[1] https://issues.apache.org/jira/browse/INFRA-3372
[2]
http://www.apache.org/dev/publishing-maven-artifacts.html#publish-snapshot
