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/11/03 15:30:49 UTC
svn commit: r1814216 - in /uima/site/trunk/uima-website:
docs/checklist-release.html docs/dev-eclipse-plugin-signing.html
xdocs/checklist-release.xml xdocs/dev-eclipse-plugin-signing.xml
Author: schor
Date: Fri Nov 3 15:30:49 2017
New Revision: 1814216
URL: http://svn.apache.org/viewvc?rev=1814216&view=rev
Log:
no jira update details for eclipse signing and pruning
Modified:
uima/site/trunk/uima-website/docs/checklist-release.html
uima/site/trunk/uima-website/docs/dev-eclipse-plugin-signing.html
uima/site/trunk/uima-website/xdocs/checklist-release.xml
uima/site/trunk/uima-website/xdocs/dev-eclipse-plugin-signing.xml
Modified: uima/site/trunk/uima-website/docs/checklist-release.html
URL: http://svn.apache.org/viewvc/uima/site/trunk/uima-website/docs/checklist-release.html?rev=1814216&r1=1814215&r2=1814216&view=diff
==============================================================================
--- uima/site/trunk/uima-website/docs/checklist-release.html (original)
+++ uima/site/trunk/uima-website/docs/checklist-release.html Fri Nov 3 15:30:49 2017
@@ -337,11 +337,30 @@ svn import -m "commit msg, e.g. uimaj-2.
be "binary" style files. (The line endings (if you build on windows) will be changed upon upload to svn,
which will result in bad signatures).
</li>
- <li>Eclipse update sites are already svn working copies, so you can commit these.
- If using Windows and have tortise svn installed, cd to the eclipse-update-site/uimaj (or wherever your update site
- was built) and right click and say commit (and click the "all" selection to upload the new files).
+ <li>Eclipse update sites:
+ <ul>
+ <li>If you a resetting the update subsite, do these steps:
+ <ol>
+ <li>rename the update subsite to xxx-a.b.c-d.e.f where a.b.c is the first version and d.e.f is the last
+ version. You do this via svn copy command in the dist.apache.org release spot.
+ If you have a GUI tool like tortisesvn, you can use that.</li>
+ <li>after the rename, wait until you see this in the archive.apache.org spot, then delete it from the
+ dist.apache.org release svn. Although this will delete it on the apache mirror system, it will remain
+ in the archive.apache.org spot.</li>
+ <li>now, checkout the dist.apache.org release subsite, and modify it by deleting items, adding items, and
+ modifying items in the working set. Then commit these changes so the current site reflects the new
+ one.</li>
+ </ol>
+ </li>
+ <li>Otherwise, the eclipse-update-sub-site project's output folder in the target directory should
+ already be svn working copies, so you can commit these.
+ If using Windows and have tortise svn installed, cd to the target/eclipse-update-site/uimaj (or wherever your update site
+ was built) and right click and say commit (and click the "all" selection to upload the new files).
+ </li>
+ </ul>
</li>
- <li>update the UIMA website docs/d with any generated docs, in a manner to
+
+ <li>update the UIMA website docs/d with any generated docs, in a manner to
<a href="saving-svn-resources.html">minimize SVN space</a> use, if possible.
This includes: PDFs, HTML versions of docbooks plus the index.html; all go on the
website under the uima.apache.org/d/ (non-SVN source) directory. Update the index.html
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=1814216&r1=1814215&r2=1814216&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 Fri Nov 3 15:30:49 2017
@@ -250,7 +250,7 @@ allows the plugin installer to avoid say
the release manager, using their special credentials, logs onto the signing portal. This process
requires a one-time code, which the portal will send to you. (Note: I had to refresh my web browser in order to
get the screen showing that option). Once signed, in, make a signing set
- consisting of all of the Jars in target/eus-work/plugins (feature jars don't need to be signed)
+ consisting of all of the Jars in target/eus-work/plugins and feature jars (feature jars must also be signed)
(not the *.pack.gz files). Test sign these and download them.
</p>
<p>For safety, make a copy of the target/eus-work/plugins directory, and then update the .jar files in that directory
@@ -261,6 +261,8 @@ allows the plugin installer to avoid say
signatures and checksums to these. These are then re-published, merging with any previous contents of the update site.
</p>
<p>Please try installing the result to confirm nothing went wrong in this re-build process.</p>
+ <p>If all is well, repeat the above process starting with selection "production" signing for the jars, downloading
+ those jars, replacing them into the eus-work directory, and re-running the mvn antrun:run@make-subsite-after-signing.</p>
</blockquote>
</td></tr>
</table>
Modified: uima/site/trunk/uima-website/xdocs/checklist-release.xml
URL: http://svn.apache.org/viewvc/uima/site/trunk/uima-website/xdocs/checklist-release.xml?rev=1814216&r1=1814215&r2=1814216&view=diff
==============================================================================
--- uima/site/trunk/uima-website/xdocs/checklist-release.xml (original)
+++ uima/site/trunk/uima-website/xdocs/checklist-release.xml Fri Nov 3 15:30:49 2017
@@ -125,6 +125,7 @@ svn import -m "commit msg, e.g. uimaj-2.
<li>Send [VOTE] message to dev list. List the staging repository that testers
will need to add to their <code>settings.xml</code> files, and the distribution SVN repo link.</li>
<li>Post RESULT message</li>
+ <li>For Eclipse plugins, <a href="dev-eclipse-plugin-signing.html">sign the jars</a>.</li>
<li>Delete any artifacts from the staging repo that aren't supposed to go to Maven Central (if any).
The uimaj build doesn't put the bin.zip or bin.tar artifacts on the staging repo, but
other builds might need some cleanup.
@@ -142,11 +143,30 @@ svn import -m "commit msg, e.g. uimaj-2.
be "binary" style files. (The line endings (if you build on windows) will be changed upon upload to svn,
which will result in bad signatures).
</li>
- <li>Eclipse update sites are already svn working copies, so you can commit these.
- If using Windows and have tortise svn installed, cd to the eclipse-update-site/uimaj (or wherever your update site
- was built) and right click and say commit (and click the "all" selection to upload the new files).
+ <li>Eclipse update sites:
+ <ul>
+ <li>If you a resetting the update subsite, do these steps:
+ <ol>
+ <li>rename the update subsite to xxx-a.b.c-d.e.f where a.b.c is the first version and d.e.f is the last
+ version. You do this via svn copy command in the dist.apache.org release spot.
+ If you have a GUI tool like tortisesvn, you can use that.</li>
+ <li>after the rename, wait until you see this in the archive.apache.org spot, then delete it from the
+ dist.apache.org release svn. Although this will delete it on the apache mirror system, it will remain
+ in the archive.apache.org spot.</li>
+ <li>now, checkout the dist.apache.org release subsite, and modify it by deleting items, adding items, and
+ modifying items in the working set. Then commit these changes so the current site reflects the new
+ one.</li>
+ </ol>
+ </li>
+ <li>Otherwise, the eclipse-update-sub-site project's output folder in the target directory should
+ already be svn working copies, so you can commit these.
+ If using Windows and have tortise svn installed, cd to the target/eclipse-update-site/uimaj (or wherever your update site
+ was built) and right click and say commit (and click the "all" selection to upload the new files).
+ </li>
+ </ul>
</li>
- <li>update the UIMA website docs/d with any generated docs, in a manner to
+
+ <li>update the UIMA website docs/d with any generated docs, in a manner to
<a href="saving-svn-resources.html">minimize SVN space</a> use, if possible.
This includes: PDFs, HTML versions of docbooks plus the index.html; all go on the
website under the uima.apache.org/d/ (non-SVN source) directory. Update the index.html
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=1814216&r1=1814215&r2=1814216&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 Fri Nov 3 15:30:49 2017
@@ -47,7 +47,7 @@ allows the plugin installer to avoid say
the release manager, using their special credentials, logs onto the signing portal. This process
requires a one-time code, which the portal will send to you. (Note: I had to refresh my web browser in order to
get the screen showing that option). Once signed, in, make a signing set
- consisting of all of the Jars in target/eus-work/plugins (feature jars don't need to be signed)
+ consisting of all of the Jars in target/eus-work/plugins and feature jars (feature jars must also be signed)
(not the *.pack.gz files). Test sign these and download them.
</p>
@@ -61,6 +61,9 @@ allows the plugin installer to avoid say
</p>
<p>Please try installing the result to confirm nothing went wrong in this re-build process.</p>
+
+ <p>If all is well, repeat the above process starting with selection "production" signing for the jars, downloading
+ those jars, replacing them into the eus-work directory, and re-running the mvn antrun:run@make-subsite-after-signing.</p>
</subsection>
<subsection name="Changes to Normal Build">