You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@avalon.apache.org by le...@apache.org on 2003/06/11 21:58:17 UTC
cvs commit: avalon/buildsystem maven.xml maven-common.xml
leosimons 2003/06/11 12:58:17
Modified: buildsystem maven.xml maven-common.xml
Log:
failing to be able to fully automate release signing, at least make it real easy.
Revision Changes Path
1.6 +7 -0 avalon/buildsystem/maven.xml
Index: maven.xml
===================================================================
RCS file: /home/cvs/avalon/buildsystem/maven.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- maven.xml 11 Jun 2003 18:13:44 -0000 1.5
+++ maven.xml 11 Jun 2003 19:58:17 -0000 1.6
@@ -176,6 +176,13 @@
maven -Doverride.version=1.3 \
-Dsend.announce=true avalon:deploy
+ For a little more info about building distributions, try
+
+ maven avalon:dist-sign
+
+ which will output the commands you need to use. Unfortunately,
+ you'll still really have to do that manually.
+
Adding a new component
======================
1.3 +47 -0 avalon/buildsystem/maven-common.xml
Index: maven-common.xml
===================================================================
RCS file: /home/cvs/avalon/buildsystem/maven-common.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- maven-common.xml 11 Jun 2003 18:12:50 -0000 1.2
+++ maven-common.xml 11 Jun 2003 19:58:17 -0000 1.3
@@ -462,6 +462,53 @@
</goal>
+ <goal name="avalon:dist-sign"
+ description="Sign the distributions using GPG">
+ <ant:echo>
+=======================================================================
+ Sorry, but it is not possible to autmoate the keysigning. You need to
+ install GnuPG or OpenPGP yourself, get yourself a key, add it to the
+ KEYS file in the root of the 'avalon' cvs module, commit the modified
+ file, upload it to daedalus.apache.org:/www/www.apache.org/dist/avalon
+ then sign the distributions you just built. Your commands might look
+ somewhat like:
+
+ cd ${maven.build.dir}/distributions
+ gpg --output ${maven.final.name}.zip.asc \
+ --detach-sig --armor ${maven.final.name}.zip
+
+ cd ${maven.build.dir}
+ gpg --output ${maven.final.name}.jar.asc \
+ --detach-sig --armor ${maven.final.name}.jar
+
+ or something similar, repeated for each file you're going to
+ distribute. If you're on linux/unix (or have cygwin), you
+ might use
+
+ cd ${maven.build.dir}/distributions
+ for i in *.zip;
+ gpg --output ${maven.final.name}.zip.asc \
+ --detach-sig --armor ${maven.final.name}.zip
+ done
+ for i in *.gz;
+ gpg --output ${maven.final.name}.zip.asc \
+ --detach-sig --armor ${maven.final.name}.zip
+ done
+
+ cd ${maven.build.dir}
+ for i in *.jar;
+ gpg --output ${maven.final.name}.jar.asc \
+ --detach-sig --armor ${maven.final.name}.jar
+ done
+
+ For more help, see
+
+ http://nagoya.apache.org/wiki/apachewiki.cgi?SigningReleases
+ http://www.gnupg.org/gph/en/manual.html
+=======================================================================
+ </ant:echo>
+ </goal>
+
<!-- ==========================================================
Deployment customization
========================================================== -->
---------------------------------------------------------------------
To unsubscribe, e-mail: cvs-unsubscribe@avalon.apache.org
For additional commands, e-mail: cvs-help@avalon.apache.org