Author: schor
Date: Thu Nov 9 17:05:30 2017
New Revision: 1814750
URL: http://svn.apache.org/viewvc?rev=1814750&view=rev
Log:
no Jira, improve signing webpage
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=1814750&r1=1814749&r2=1814750&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 Thu Nov
9 17:05:30 2017
@@ -225,9 +225,14 @@
<blockquote class="sectionBody">
<p>All released Apache artifacts are
normally signed. Eclipse jar signing is in addition
to the Apache release signing. This additional signing (with a recognized
authority certificate)
-allows the plugin installer to avoid saying it is installing unsigned
artifacts and needs permission to continue.
+allows the Eclipse installer to avoid saying it is installing unsigned
artifacts and needs permission to continue.
</p>
- <p>Both the feature jars and
the plugin jars are signed. Feature Jars might not need signing - but it
doesn't hurt.</p>
+ <p>
+It also enables automatic notification and subsequent update (if the user
chooses) of upgrades. Because of this,
+insure your feature id's are different for versions which should not
automatically update. For instance,
+the uimav3 vs the v2 - looks
+</p>
+ <p>Both the feature jars and
the plugin jars need to be signed.</p>
<table
class="subsectionTable">
<tr><td>
@@ -332,9 +337,11 @@ allows the plugin installer to avoid say
</td></tr>
<tr><td>
<blockquote class="sectionBody">
- <p>See
https://reference.apache.org/pmc/codesigning for general information.
+ <p>See <a target="_blank"
href="https://reference.apache.org/pmc/codesigning";>
+ https://reference.apache.org/pmc/codesigning</a> for general information.
</p>
- <p>See
https://wiki.eclipse.org/JAR_Signing#What_gets_signed.3F for background on
signing Eclipse Plugins.</p>
+ <p>See <a target="_blank"
href="https://wiki.eclipse.org/JAR_Signing#What_gets_signed";>
+ https://wiki.eclipse.org/JAR_Signing#What_gets_signed</a> for background on
signing Eclipse Plugins.</p>
</blockquote>
</p>
</td></tr>
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=1814750&r1=1814749&r2=1814750&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 Thu Nov
9 17:05:30 2017
@@ -29,10 +29,16 @@ under the License.
<section name="Overview">
<p>All released Apache artifacts are normally signed. Eclipse jar signing is
in addition
to the Apache release signing. This additional signing (with a recognized
authority certificate)
-allows the plugin installer to avoid saying it is installing unsigned
artifacts and needs permission to continue.
+allows the Eclipse installer to avoid saying it is installing unsigned
artifacts and needs permission to continue.
</p>
-<p>Both the feature jars and the plugin jars are signed. Feature Jars might
not need signing - but it doesn't hurt.</p>
+<p>
+It also enables automatic notification and subsequent update (if the user
chooses) of upgrades. Because of this,
+insure your feature id's are different for versions which should not
automatically update. For instance,
+the uimav3 vs the v2 - looks
+</p>
+
+<p>Both the feature jars and the plugin jars need to be signed.</p>
<subsection name="Process Flow">
<p>We use a 2 step process, to reduce costs to Apache for signing release
candidates which subsequently fail.
@@ -95,9 +101,11 @@ allows the plugin installer to avoid say
</section>
<section name="Links to Apache resources for codesigning">
- <p>See https://reference.apache.org/pmc/codesigning for general information.
+ <p>See <a target="_blank"
href="https://reference.apache.org/pmc/codesigning";>
+ https://reference.apache.org/pmc/codesigning</a> for general information.
</p>
- <p>See https://wiki.eclipse.org/JAR_Signing#What_gets_signed.3F for
background on signing Eclipse Plugins.</p>
+ <p>See <a target="_blank"
href="https://wiki.eclipse.org/JAR_Signing#What_gets_signed";>
+ https://wiki.eclipse.org/JAR_Signing#What_gets_signed</a> for background on
signing Eclipse Plugins.</p>
</section>
<section name="Release Flow">
