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/26 16:00:30 UTC
svn commit: r1813422 - in /uima/site/trunk/uima-website:
docs/dev-eclipse-plugin-archiving.html xdocs/dev-eclipse-plugin-archiving.xml
Author: schor
Date: Thu Oct 26 16:00:30 2017
New Revision: 1813422
URL: http://svn.apache.org/viewvc?rev=1813422&view=rev
Log:
no jira, version 2 of how to archive old eclipse plugin versions
Modified:
uima/site/trunk/uima-website/docs/dev-eclipse-plugin-archiving.html
uima/site/trunk/uima-website/xdocs/dev-eclipse-plugin-archiving.xml
Modified: uima/site/trunk/uima-website/docs/dev-eclipse-plugin-archiving.html
URL: http://svn.apache.org/viewvc/uima/site/trunk/uima-website/docs/dev-eclipse-plugin-archiving.html?rev=1813422&r1=1813421&r2=1813422&view=diff
==============================================================================
--- uima/site/trunk/uima-website/docs/dev-eclipse-plugin-archiving.html (original)
+++ uima/site/trunk/uima-website/docs/dev-eclipse-plugin-archiving.html Thu Oct 26 16:00:30 2017
@@ -226,9 +226,7 @@
<p>The Eclipse Update Site holds a multi-update-site root, which, in turn, links to various subsites (for various projects).
Each of those subsites typically has several versions of the plugins; a release process adds fresh versions of plugins to that site.
</p>
- <p>At some point, there are too many versions, and it makes sense to archive these older ones.
- To do this you need to run Eclipse special tooling to keep the artifacts.jar and content.jar artifacts
- in sync with the features and plugins.
+ <p>At some point, there are too many versions, and it makes sense to archive these older ones.
</p>
</blockquote>
</p>
@@ -267,9 +265,8 @@
<ul>
<li>A subsite is started (e.g. ruta, or uimaj)</li>
<li>Releases occur, and plugins are added at some version level</li>
- <li>After some number of releases, a decision is made that the repo is getting too big.
- At that point, a small number (default, just the most recent) version is sliced off
- into another repo.</li>
+ <li>After some number of releases, a decision is made that the repo is getting too big.</li>
+
<li>The old repo is renamed with a suffix indicating the range of versions in it. For example,
the "uimaj" repo might have a name uimaj-2.3.1-2.10.0.</li>
<li>The new slice repo, with perhaps just one (the latest version) is then deployed.
@@ -289,27 +286,26 @@
<div class="sectionTable">
<table class="sectionTable">
<tr><td>
- <a name="Doing the slicing and updating the site"><h1><img src="images/UIMA_4sq50tightCropSolid.png"/> Doing the slicing and updating the site</h1></a>
+ <a name="Resetting the update site for a new batch of versions"><h1><img src="images/UIMA_4sq50tightCropSolid.png"/> Resetting the update site for a new batch of versions</h1></a>
</td></tr>
<tr><td>
<blockquote class="sectionBody">
- <p>The eclipse ant tasks for maintaining update sites are documented here:
- https://help.eclipse.org/oxygen/index.jsp?topic=%2Forg.eclipse.platform.doc.isv%2Fguide%2Fp2_repositorytasks.htm .
- </p>
- <p>This ant task is used in a Maven project, located in uima/build, named:
- <a target="_blank" href="http://svn.apache.org/repos/asf/uima/build/trunk/uima-eclipse-update-site-slicing/">
- uima-eclipse-update-site-slicing</a>.
- This does the slicing described above. To use, check out this project as a maven project (it's not a Java project), and
- read the readme.txt, and follow the instructions.</p>
- <p>When it runs, it reads the existing subsite directly from the dist.apache.org repository, and builds the request slice
- in the project's target/eclipse-update-site/---subsite--- directory.</p>
- <p>To complete the maintenance, do these steps in the dist.apache.org svn release eclipse-update-site:
- <ol>
- <li>Do a sanity test of the new subsite - try installing it into a fresh Eclipse install.</li>
- <li>svn mv to rename the current subsite to the versioned name.</li>
- <li>once it appears on the archive spot, do an svn delete to remove it </li>
- <li>import the new (pruned) subsite to the release spot.</li>
- </ol></p>
+ <p>Here is the procedure to reset the update site for a new batch of versions, going forward.
+ <ul>
+ <li>Rename the existing update site with a suffix indicating the range of versions. For
+ example, uimaj would be renamed to uimaj-2.3.1-2.10.1 </li>
+ <li>generate the new site using a version of the update site pom which skips the steps
+ that copy the previous site. This results in the new update site only having the
+ current version.</li>
+ </ul>
+</p>
+ <p>
+ After the rename has been copied to https://archive.apache.org/dist/uima/eclipse-update-site/xxxx
+ delete this from the main distribution site.
+</p>
+ <p>Do the renaming then deleting using svn repository commands. SVN doesn't have a rename command, so
+ use a copy then delete of the old one. You can also use a GUI like TortiseSvn.
+</p>
</blockquote>
</p>
</td></tr>
Modified: uima/site/trunk/uima-website/xdocs/dev-eclipse-plugin-archiving.xml
URL: http://svn.apache.org/viewvc/uima/site/trunk/uima-website/xdocs/dev-eclipse-plugin-archiving.xml?rev=1813422&r1=1813421&r2=1813422&view=diff
==============================================================================
--- uima/site/trunk/uima-website/xdocs/dev-eclipse-plugin-archiving.xml (original)
+++ uima/site/trunk/uima-website/xdocs/dev-eclipse-plugin-archiving.xml Thu Oct 26 16:00:30 2017
@@ -31,9 +31,7 @@ under the License.
Each of those subsites typically has several versions of the plugins; a release process adds fresh versions of plugins to that site.
</p>
-<p>At some point, there are too many versions, and it makes sense to archive these older ones.
- To do this you need to run Eclipse special tooling to keep the artifacts.jar and content.jar artifacts
- in sync with the features and plugins.
+<p>At some point, there are too many versions, and it makes sense to archive these older ones.
</p>
</section>
@@ -58,9 +56,8 @@ under the License.
<ul>
<li>A subsite is started (e.g. ruta, or uimaj)</li>
<li>Releases occur, and plugins are added at some version level</li>
- <li>After some number of releases, a decision is made that the repo is getting too big.
- At that point, a small number (default, just the most recent) version is sliced off
- into another repo.</li>
+ <li>After some number of releases, a decision is made that the repo is getting too big.</li>
+
<li>The old repo is renamed with a suffix indicating the range of versions in it. For example,
the "uimaj" repo might have a name uimaj-2.3.1-2.10.0.</li>
<li>The new slice repo, with perhaps just one (the latest version) is then deployed.
@@ -77,7 +74,8 @@ under the License.
</section>
-<section name="Doing the slicing and updating the site">
+<section name="Resetting the update site for a new batch of versions">
+ <!--
<p>The eclipse ant tasks for maintaining update sites are documented here:
https://help.eclipse.org/oxygen/index.jsp?topic=%2Forg.eclipse.platform.doc.isv%2Fguide%2Fp2_repositorytasks.htm .
</p>
@@ -89,7 +87,7 @@ under the License.
read the readme.txt, and follow the instructions.</p>
<p>When it runs, it reads the existing subsite directly from the dist.apache.org repository, and builds the request slice
- in the project's target/eclipse-update-site/---subsite--- directory.</p>
+ in the project's target/eclipse-update-site/- - -subsite- - - directory.</p>
<p>To complete the maintenance, do these steps in the dist.apache.org svn release eclipse-update-site:
<ol>
@@ -97,7 +95,24 @@ under the License.
<li>svn mv to rename the current subsite to the versioned name.</li>
<li>once it appears on the archive spot, do an svn delete to remove it </li>
<li>import the new (pruned) subsite to the release spot.</li>
- </ol></p>
+ </ol></p>
+ -->
+ <p>Here is the procedure to reset the update site for a new batch of versions, going forward.
+ <ul>
+ <li>Rename the existing update site with a suffix indicating the range of versions. For
+ example, uimaj would be renamed to uimaj-2.3.1-2.10.1 </li>
+ <li>generate the new site using a version of the update site pom which skips the steps
+ that copy the previous site. This results in the new update site only having the
+ current version.</li>
+ </ul>
+</p>
+<p>
+ After the rename has been copied to https://archive.apache.org/dist/uima/eclipse-update-site/xxxx
+ delete this from the main distribution site.
+</p>
+<p>Do the renaming then deleting using svn repository commands. SVN doesn't have a rename command, so
+ use a copy then delete of the old one. You can also use a GUI like TortiseSvn.
+</p>
</section>
</body>