m2 gpg plugin (was Re: Update of ReleasePlan105 by GregReddin)

2008-05-12 Thread Rahul Akolkar
On 5/12/08, Apache Wiki [EMAIL PROTECTED] wrote:
 Dear Wiki user,

  You have subscribed to a wiki page or wiki category on Shale Wiki for 
 change notification.

  The following page has been changed by GregReddin:
  http://wiki.apache.org/shale/ReleasePlan105

  
 --
   Maven did not do the GPG signing bit so I performed the following steps:

snip/

Its sometimes tedious to figure out why certain things are not
happening in the m2 build, but I think it'll be worthwhile spending
some time trying to fix this -- it will be a lot of work if you have
to manually sign the artifacts in the framework release(s).

-Rahul


   {{{
  - cd target/
  + cd target/checkout
   gpg --armor --output shale-master-3.pom.asc --detach-sig pom.xml
   scp shale-master-3.pom.asc 
 people.apache.org:/www/people.apache.org/builds/shale/m2-staging-repository/org/apache/shale/shale-master/3/.
   }}}



Re: m2 gpg plugin (was Re: Update of ReleasePlan105 by GregReddin)

2008-05-12 Thread Greg Reddin
On Mon, May 12, 2008 at 11:18 AM, Rahul Akolkar [EMAIL PROTECTED] wrote:
  Its sometimes tedious to figure out why certain things are not
  happening in the m2 build, but I think it'll be worthwhile spending
  some time trying to fix this -- it will be a lot of work if you have
  to manually sign the artifacts in the framework release(s).

True, I didn't think about that. I'll look into it. I saw something
somewhere about the GPG plugin. I'm sure I can figure out how to add
that goal to the release process.

Greg


Re: m2 gpg plugin (was Re: Update of ReleasePlan105 by GregReddin)

2008-05-12 Thread Rahul Akolkar
On 5/12/08, Greg Reddin [EMAIL PROTECTED] wrote:
 On Mon, May 12, 2008 at 11:18 AM, Rahul Akolkar [EMAIL PROTECTED] wrote:
Its sometimes tedious to figure out why certain things are not
happening in the m2 build, but I think it'll be worthwhile spending
some time trying to fix this -- it will be a lot of work if you have
to manually sign the artifacts in the framework release(s).


 True, I didn't think about that. I'll look into it. I saw something
  somewhere about the GPG plugin. I'm sure I can figure out how to add
  that goal to the release process.

snip/

Ah, we don't have it in master :-) I think thats OK for now. Its
already there in the release profile in the parent ...

  http://svn.apache.org/repos/asf/shale/framework/trunk/pom.xml

... so adding -Prelease should get that going for the framework releases.

-Rahul



  Greg