It should be noted, Wendy was kind enough after 1.3.6 to add a "release"
profile to run the GPG plugin. But I forgot about it and did the 1.3.7
deployment of the signing by hand :-) Silly me for not remembering!
Paul
Wendy Smoak wrote:
On 2/25/07, Ted Husted <[EMAIL PROTECTED]> wrote:
Could you specify the exact steps that we should be following then?
I added a TODO to review steps 5 and 6 on the wiki page. You
mentioned March 4th for Struts 2.0.7, so that gives me a few days.
(I'd like to see Struts start using the release plugin, but I need to
spend some time with it and make sure everything is in place before I
suggest changing the release process, which is working well enough.
Maven releases should be easier than this!)
I use Cygwin exclusively, so I'm not having the back-and-forth issues
that you describe... and that's going to be difficult to troubleshoot
remotely. :( How about creating a ssh key with Cygwin, and appending
it to to your authorized_keys on people.a.o?
Paul, it sounds like the Struts 1 process is having a similar
problem, because 'mvn deploy' with the gpg plugin configured should
upload the signatures automatically along with the jars and poms.
Thanks again to our release managers! I don't have time to take it on
again right now, but I will make time to help if anyone else would
like to learn the process.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
