You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@uima.apache.org by sc...@apache.org on 2017/10/10 15:58:15 UTC
svn commit: r1811734 - in /uima/site/trunk/uima-website:
docs/dev-eclipse-plugin-signing.html xdocs/dev-eclipse-plugin-signing.xml
Author: schor
Date: Tue Oct 10 15:58:15 2017
New Revision: 1811734
URL: http://svn.apache.org/viewvc?rev=1811734&view=rev
Log:
[UIMA-5583] improve method for signing
Modified:
uima/site/trunk/uima-website/docs/dev-eclipse-plugin-signing.html
uima/site/trunk/uima-website/xdocs/dev-eclipse-plugin-signing.xml
Modified: uima/site/trunk/uima-website/docs/dev-eclipse-plugin-signing.html
URL: http://svn.apache.org/viewvc/uima/site/trunk/uima-website/docs/dev-eclipse-plugin-signing.html?rev=1811734&r1=1811733&r2=1811734&view=diff
==============================================================================
--- uima/site/trunk/uima-website/docs/dev-eclipse-plugin-signing.html (original)
+++ uima/site/trunk/uima-website/docs/dev-eclipse-plugin-signing.html Tue Oct 10 15:58:15 2017
@@ -241,8 +241,8 @@ allows the plugin installer to avoid say
<tr><td>
<blockquote class="subsectionBody">
<p>We use a 2 step process, to reduce costs to Apache for signing release candidates which subsequently fail.
- After the release vote passes, two subsequent Ant tasks are run to rebuild the update site, from the
- tag, with a manual (at this point) signing step for the Jars, inbetween them.</p>
+ After the release vote passes, plugin Jar files are manually uploaded and signed,
+ and then a subsequent Ant task is run to rebuild the site packaging artifacts.</p>
<p>The first step is to do a normal build of the update site, using mvn release:prepare.
This produces the artifacts for voting on, without signing the
new plugin Jars, and writes the "tag" for this into SVN for record keeping.</p>
Modified: uima/site/trunk/uima-website/xdocs/dev-eclipse-plugin-signing.xml
URL: http://svn.apache.org/viewvc/uima/site/trunk/uima-website/xdocs/dev-eclipse-plugin-signing.xml?rev=1811734&r1=1811733&r2=1811734&view=diff
==============================================================================
--- uima/site/trunk/uima-website/xdocs/dev-eclipse-plugin-signing.xml (original)
+++ uima/site/trunk/uima-website/xdocs/dev-eclipse-plugin-signing.xml Tue Oct 10 15:58:15 2017
@@ -36,8 +36,8 @@ allows the plugin installer to avoid say
<subsection name="Process Flow">
<p>We use a 2 step process, to reduce costs to Apache for signing release candidates which subsequently fail.
- After the release vote passes, two subsequent Ant tasks are run to rebuild the update site, from the
- tag, with a manual (at this point) signing step for the Jars, inbetween them.</p>
+ After the release vote passes, plugin Jar files are manually uploaded and signed,
+ and then a subsequent Ant task is run to rebuild the site packaging artifacts.</p>
<p>The first step is to do a normal build of the update site, using mvn release:prepare.
This produces the artifacts for voting on, without signing the