You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@uima.apache.org by tw...@apache.org on 2009/07/02 11:18:15 UTC
svn commit: r790515 - in /incubator/uima/site/trunk/uima-website:
docs/distribution.html xdocs/distribution.xml
Author: twgoetz
Date: Thu Jul 2 09:18:14 2009
New Revision: 790515
URL: http://svn.apache.org/viewvc?rev=790515&view=rev
Log:
Jira UIMA-1411: fix instructions for building eclipse update site.
https://issues.apache.org/jira/browse/UIMA-1411
Modified:
incubator/uima/site/trunk/uima-website/docs/distribution.html
incubator/uima/site/trunk/uima-website/xdocs/distribution.xml
Modified: incubator/uima/site/trunk/uima-website/docs/distribution.html
URL: http://svn.apache.org/viewvc/incubator/uima/site/trunk/uima-website/docs/distribution.html?rev=790515&r1=790514&r2=790515&view=diff
==============================================================================
--- incubator/uima/site/trunk/uima-website/docs/distribution.html (original)
+++ incubator/uima/site/trunk/uima-website/docs/distribution.html Thu Jul 2 09:18:14 2009
@@ -223,26 +223,24 @@
</p>
<p>
The Eclipse update site is built in 2 phases. The first phase occurs during the normal maven
- builds of the project - this phase builds the Jars that constitute the plugins, and builds the
- Jars that package up the feature specifications.
- The feature Jars do not actually contain any Java classes;
- the Jar format is just to consolidate and compress the file contents.
+ builds of the project - this phase builds the Jars that constitute the plugins.
</p>
<p>
The second phase occurs after a release is approved, and consists of several parts:
<ul>
<li>Any new Plugin Jars are packed</li>
+ <li>The feature jars are generated</li>
<li>The Site.xml is updated to include the any new components / versions</li>
<li>The site digest is regenerated</li>
</ul>
</p>
<p>These steps are carried out by running the build.xml script with "ant" in the
- uimaj-eclipse-update-site project, after placing any new feature jars from the
- approved release candidate in the "features" folder, and any new plugin jars
+ uimaj-eclipse-update-site project, after placing any new plugin jars
from the approved release candidate in the "plugins" folder. The "plugins" folder should
not have any other jars in it (other than the new ones which will be packed);
the "features" folder is saved in SVN and accumulates the
- feature Jars for all the features/versions.
+ feature Jars for all the features/versions. The feature Jars do not actually contain any Java classes;
+ the Jar format is just to consolidate and compress the file contents.
</p>
<p>
The result of running the build.xml is a partial eclipse update site
Modified: incubator/uima/site/trunk/uima-website/xdocs/distribution.xml
URL: http://svn.apache.org/viewvc/incubator/uima/site/trunk/uima-website/xdocs/distribution.xml?rev=790515&r1=790514&r2=790515&view=diff
==============================================================================
--- incubator/uima/site/trunk/uima-website/xdocs/distribution.xml (original)
+++ incubator/uima/site/trunk/uima-website/xdocs/distribution.xml Thu Jul 2 09:18:14 2009
@@ -74,27 +74,25 @@
</p>
<p>
The Eclipse update site is built in 2 phases. The first phase occurs during the normal maven
- builds of the project - this phase builds the Jars that constitute the plugins, and builds the
- Jars that package up the feature specifications.
- The feature Jars do not actually contain any Java classes;
- the Jar format is just to consolidate and compress the file contents.
+ builds of the project - this phase builds the Jars that constitute the plugins.
</p>
<p>
The second phase occurs after a release is approved, and consists of several parts:
<ul>
<li>Any new Plugin Jars are packed</li>
+ <li>The feature jars are generated</li>
<li>The Site.xml is updated to include the any new components / versions</li>
<li>The site digest is regenerated</li>
</ul>
</p>
<p>These steps are carried out by running the build.xml script with "ant" in the
- uimaj-eclipse-update-site project, after placing any new feature jars from the
- approved release candidate in the "features" folder, and any new plugin jars
+ uimaj-eclipse-update-site project, after placing any new plugin jars
from the approved release candidate in the "plugins" folder. The "plugins" folder should
not have any other jars in it (other than the new ones which will be packed);
the "features" folder is saved in SVN and accumulates the
- feature Jars for all the features/versions.
+ feature Jars for all the features/versions. The feature Jars do not actually contain any Java classes;
+ the Jar format is just to consolidate and compress the file contents.
</p>
<p>