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 2008/03/02 17:14:19 UTC
svn commit: r632778 - in /incubator/uima/site/trunk/uima-website:
docs/svn.html xdocs/svn.xml
Author: schor
Date: Sun Mar 2 08:14:19 2008
New Revision: 632778
URL: http://svn.apache.org/viewvc?rev=632778&view=rev
Log:
[UIMA-836] Fix doc on website to indicate top level dir for eclipse-home doesn't need to be called "eclipse". Also clarify the need to run "install" before eclipse:eclipse, and why (needed for eclipse plugin projects). Also, clean up formatting to allow browser window to be less wide (some <pre> lines were excessively long, others had breaks indicated with "\" in the wrong places).
Modified:
incubator/uima/site/trunk/uima-website/docs/svn.html
incubator/uima/site/trunk/uima-website/xdocs/svn.xml
Modified: incubator/uima/site/trunk/uima-website/docs/svn.html
URL: http://svn.apache.org/viewvc/incubator/uima/site/trunk/uima-website/docs/svn.html?rev=632778&r1=632777&r2=632778&view=diff
==============================================================================
--- incubator/uima/site/trunk/uima-website/docs/svn.html (original)
+++ incubator/uima/site/trunk/uima-website/docs/svn.html Sun Mar 2 08:14:19 2008
@@ -274,12 +274,10 @@
<tr><td>
<blockquote>
<p>Use a command like:</p>
- <pre>% svn checkout http://svn.apache.org/repos/asf/incubator/uima/uimaj/trunk </pre>
+ <longquote>% svn checkout http://svn.apache.org/repos/asf/incubator/uima/uimaj/trunk<code /></longquote>
<p>Once you have Apache UIMA checked out you can update the source
by executing the following command from within the UIMA directory. </p>
- <pre>
-% svn update
-</pre>
+ <longquote><code>% svn update</code></longquote>
</blockquote>
</td></tr>
<tr><td><br/></td></tr>
@@ -297,9 +295,8 @@
<p>For those users who are stuck behind a corporate firewall which is
blocking http access to the Subversion repository, you can try to access it
via HTTPS: </p>
- <pre>
-% svn checkout https://svn.apache.org/repos/asf/incubator/uima/uimaj/trunk
-</pre>
+ <longquote><code>% svn checkout \<br />
+ https://svn.apache.org/repos/asf/incubator/uima/uimaj/trunk</code></longquote>
</blockquote>
</td></tr>
<tr><td><br/></td></tr>
@@ -326,11 +323,11 @@
</p>
<p>Example : Edit the 'servers' file and add something like :
</p>
- <pre>
+ <longquote><pre>
[global]
http-proxy-host = your.proxy.name
http-proxy-port = 3128
-</pre>
+</pre></longquote>
</blockquote>
</td></tr>
<tr><td><br/></td></tr>
@@ -349,9 +346,8 @@
but Apache UIMA Committers must checkout the Subversion repository
via HTTPS.
</p>
- <pre>
-% svn checkout https://svn.apache.org/repos/asf/incubator/uima/uimaj/trunk
-</pre>
+ <longquote><code>% svn checkout \<br />
+ https://svn.apache.org/repos/asf/incubator/uima/uimaj/trunk</code></longquote>
</blockquote>
</td></tr>
<tr><td><br/></td></tr>
@@ -422,9 +418,9 @@
description, or your initials, e.g.
UIMA-104.clr.patch
</p>
- <pre>
+ <longquote><pre>
% svn diff > UIMA-104.clr.patch
-</pre>
+</pre></longquote>
</blockquote>
</td></tr>
<tr><td><br/></td></tr>
@@ -448,19 +444,20 @@
<p>
Once your password is set, you can use a command like this to commit:
</p>
- <pre>
-$> svn commit --username your-username
-Authentication realm: <https://svn.apache.org:443> ASF Committers
-Password for 'your-username': your-password
-</pre>
+ <longquote><pre>
+$> svn commit --username your-username \
+ Authentication realm: <https://svn.apache.org:443> \
+ ASF Committers Password for 'your-username': your-password
+</pre></longquote>
<p>You can also pass your password on the command line directly, but
this is a security problem on multiuser unix computers (the command line
arguments are available via the ps command). Here is the command if you
are Windows or a single user unix computer:
</p>
- <pre>
-$> svn commit --username your-username --password your-password
-</pre>
+ <longquote><pre>
+$> svn commit --username your-username \
+ --password your-password
+</pre></longquote>
<p>Remember to replace 'your-username' and 'your-password' with
your actual username and password on svn.apache.org.
</p>
@@ -468,9 +465,10 @@
Please also add to your commit statement an appropriate message that explains the changes you did.
You can add a message when adding <code>--message</code> to your commit statement:
</p>
- <pre>
-$> svn commit --username your-username --password your-password --message your-message
-</pre>
+ <longquote><pre>
+$> svn commit --username your-username \
+ --password your-password --message your-message
+</pre></longquote>
<p>
Please always enter the JIRA issue key and additionally the JIRA issue link
to the commit message. The issue key (e.g., UIMA-555) is important so that the JIRA SVN plugin can detect the
@@ -517,25 +515,26 @@
<tr><td>
<blockquote>
<p>
-<pre>
+<longquote><pre>
$> cd uimaj
$> mvn install
-</pre>
+</pre></longquote>
</p>
<p>
The first time you try this, you will probably get an error that <code>javax:activation:activation:jar:1.0.2</code> is not found. To resolve this,
download <code>activation.jar</code> from <a class="external" rel="nofollow" href="http://java.sun.com/products/archive/javabeans/jaf102.html">
http://java.sun.com/products/archive/javabeans/jaf102.html
</a> and execute the command:
-<pre>
-$> mvn install:install-file -DgroupId=javax.activation -DartifactId=activation -Dversion=1.0.2
- \ -Dpackaging=jar -Dfile=/path/to/file/activation.jar
-</pre>
-
+<longquote><pre>
+$> mvn install:install-file \
+ -DgroupId=javax.activation \
+ -DartifactId=activation \
+ -Dversion=1.0.2 \
+ -Dpackaging=jar \
+ -Dfile=/path/to/file/activation.jar
+</pre></longquote>
then re-run the UIMA build with the command:
-<pre>
-$> mvn install
-</pre>
+<longquote><pre>$> mvn install</pre></longquote>
</p>
<p>
This should build all of the jars and run the unit tests. Each jar will be located under the <code>target</code> subdirectory of its project, for example <code>uimaj-core/target/uima-core.jar</code>.
@@ -558,32 +557,43 @@
<blockquote>
<p>
<ol>
- <li>First, follow all the steps under "Building from the command line, above." You
- will only need to do this once.</li>
- <li>(Optional) If you want a new workspace for the maven work, start Eclipse and create a new workspace. </li>
- <li>In a command window, execute
- <br />
- <code>mvn -Declipse.workspace=<eclipse workspace dir> eclipse:add-maven-repo</code>
- <br /> This adds a maven repository to your machine (On Windows, under documents & settings / .m2 /
- repository), and sets up an Eclipse Java Build Path variable to reference it.</li>
- <li>Use Eclipse's SVN Repository explorer to checkout all the projects under uimaj/trunk. Tell it to create
- new Java projects for these.</li>
- <li>
+ <li><p>First, follow all the steps under "Building from the command line, above." You
+ will only need to do this once.</p></li>
+ <li><p>(Optional) If you want a new workspace for the maven work, start Eclipse and create a new workspace. </p></li>
+ <li><p>In a command window, execute
+ <blockquote>
+ <pre>
+mvn -Declipse.workspace=<eclipse workspace dir> \
+ eclipse:add-maven-repo</pre>
+ </blockquote>
+ This adds a maven repository to your machine (On Windows, under documents & settings / .m2 /
+ repository), and sets up an Eclipse Java Build Path variable to reference it.</p></li>
+ <li><p>Use Eclipse's SVN Repository explorer to checkout all the projects under uimaj/trunk. Tell it to create
+ new Java projects for these.</p></li>
+ <li><p>
<code>cd uimaj</code> to switch to the Eclipse workspace for the uimaj project itself is (it has the top level
POM), and run the command:
- <br />
- <code>mvn eclipse:eclipse</code>
- <br /> If you notice error messages that components need to be downloaded from the maven repository, it might
+ <blockquote><code>mvn eclipse:eclipse</code></blockquote>
+ </p><p>
+ If you haven't run the "install" using maven (because you forgot to follow all the steps under
+ "Building from the command line, above"), you should do the command
+ <code>mvn install eclipse:eclipse</code>. The "install" argument builds UIMA using maven,
+ before the eclipse:eclipse goal is run. This
+ is needed for the Eclipse Plugins that are part of UIMA - these projects have their
+ "MANIFEST.MF" file built by maven from the information in the maven POMs. This step
+ may take a few minutes because the "install" lifecycle includes running the unit tests.
+ </p><p>
+ If you notice error messages that components need to be downloaded from the maven repository, it might
tell you to redo the command using the
- <code>-DdownloadSources=true</code> parameter in order to check remote repositories for sources.</li>
- <li>Return to Eclipse, and if needed, select all the projects and push F5 to "refresh" them (because the
+ <code>-DdownloadSources=true</code> parameter in order to check remote repositories for sources.</p></li>
+ <li><p>Return to Eclipse, and if needed, select all the projects and push F5 to "refresh" them (because the
previous command changed the .project and .classpath files). You can set your workspace to automatically
- refresh - in which case skip this step.</li>
- <li>The projects should now compile without errors, and have build paths which reference copies of things in
- your local maven repository.</li>
- <li>You can run the unit tests in Eclipse by right-clicking on a folder (for example
+ refresh - in which case skip this step.</p></li>
+ <li><p>The projects should now compile without errors, and have build paths which reference copies of things in
+ your local maven repository.</p></li>
+ <li><p>You can run the unit tests in Eclipse by right-clicking on a folder (for example
<code>uimaj-core/src/test/java</code>) and selecting Run As -> JUnit Test. This will run all tests
- under that folder.</li>
+ under that folder.</p></li>
</ol>
</p>
</blockquote>
@@ -609,7 +619,7 @@
<p>
If not using Eclipse, you can use <code>grep</code> to accomplish the same thing.
</p>
- <p>You can bypass the tests by doing mvn -Dmaven.test.skip=true install. But please do this only
+ <p>You can bypass the tests by doing mvn -Dmaven.test.skip install. But please do this only
after you've run without it and have verified the tests results.</p>
</blockquote>
</td></tr>
@@ -630,8 +640,11 @@
version 3.3 or later installed, and you have to indicate to maven where it is installed.
In the examples below, this is shown as c:/your/path/to/eclipse.
Note that you can type the slashes '/' as backslashes '\' in Windows -- it doesn't matter
- (both work). The path should be to an directory named "eclipse" containing as subdirectories folders such as
- "plugins" and "features"</p>
+ (both work). The path should be to an directory (which, by default is
+ often named "eclipse" but can be named anything) containing the eclipse
+ executable, and the subdirectory folders for Eclipse such as "plugins"
+ and "features".
+ </p>
<p>
You can do this in one of 3 ways.
</p>
@@ -644,8 +657,9 @@
<pre>
<settings xmlns="http://maven.apache.org/POM/4.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
- xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
- http://maven.apache.org/xsd/settings-1.0.0.xsd">
+ xsi:schemaLocation=
+ "http://maven.apache.org/POM/4.0.0
+ http://maven.apache.org/xsd/settings-1.0.0.xsd">
<profiles>
<profile>
<id>local-build-configuration</id>
@@ -653,26 +667,30 @@
<activeByDefault>true</activeByDefault>
</activation>
<properties>
- <uima-maven-build-eclipse-home>c:/your/path/to/eclipse</uima-maven-build-eclipse-home>
+ <uima-maven-build-eclipse-home>
+ c:/your/path/to/eclipse
+ </uima-maven-build-eclipse-home>
</properties>
</profile>
</profiles>
<activeProfiles>
- <activeProfile>local-build-configuration</activeProfile>
+ <activeProfile>
+ local-build-configuration
+ </activeProfile>
</activeProfiles>
</settings>
</pre>
<p>The second way to do this is to set an environment variable. Here's an example in Windows:</p>
- <pre>set ECLIPSE_HOME=c:/your/path/to/eclipse</pre>
+ <longquote><code>set ECLIPSE_HOME=c:/your/path/to/eclipse</code></longquote>
<p>The third way is to pass a command line argument to the maven command below, which looks like this:</p>
- <pre>-Duima-maven-build-eclipse-home=c:/your/path/to/eclipse</pre>
+ <longquote><code>-Duima-maven-build-eclipse-home=c:/your/path/to/eclipse</code></longquote>
<p>
To build a distribution, first do a build as described in "Building from the command line".
Then (assuming you set up the Eclipse path using one of the first 2 methods, execute the following:
-<pre>
+<longquote><pre>
$>cd ../uimaj-distr
$>mvn assembly:assembly
-</pre>
+</pre></longquote>
This will build the javadocs and the manual (using docbooks, as described below), will create the
Eclipse update site for the Eclipse plugins, and will create
Modified: incubator/uima/site/trunk/uima-website/xdocs/svn.xml
URL: http://svn.apache.org/viewvc/incubator/uima/site/trunk/uima-website/xdocs/svn.xml?rev=632778&r1=632777&r2=632778&view=diff
==============================================================================
--- incubator/uima/site/trunk/uima-website/xdocs/svn.xml (original)
+++ incubator/uima/site/trunk/uima-website/xdocs/svn.xml Sun Mar 2 08:14:19 2008
@@ -107,22 +107,18 @@
<subsection name="Anonymous check out from Subversion" id="anonymous.checkout">
<p>Use a command like:</p>
-<pre>% svn checkout http://svn.apache.org/repos/asf/incubator/uima/uimaj/trunk </pre>
+ <longquote>% svn checkout http://svn.apache.org/repos/asf/incubator/uima/uimaj/trunk<code></code></longquote>
<p>Once you have Apache UIMA checked out you can update the source
by executing the following command from within the UIMA directory. </p>
-<pre>
-% svn update
-</pre>
+<longquote><code>% svn update</code></longquote>
</subsection>
<subsection name="Access from behind a firewall" id="access.firewall">
<p>For those users who are stuck behind a corporate firewall which is
blocking http access to the Subversion repository, you can try to access it
via HTTPS: </p>
-<pre>
-% svn checkout https://svn.apache.org/repos/asf/incubator/uima/uimaj/trunk
-</pre>
-
+<longquote><code>% svn checkout \<br/>
+ https://svn.apache.org/repos/asf/incubator/uima/uimaj/trunk</code></longquote>
</subsection>
<subsection name="Access through a proxy" id="access.proxy">
@@ -138,11 +134,11 @@
</p>
<p>Example : Edit the 'servers' file and add something like :
</p>
-<pre>
+<longquote><pre>
[global]
http-proxy-host = your.proxy.name
http-proxy-port = 3128
-</pre>
+</pre></longquote>
</subsection>
@@ -152,9 +148,8 @@
but Apache UIMA Committers must checkout the Subversion repository
via HTTPS.
</p>
-<pre>
-% svn checkout https://svn.apache.org/repos/asf/incubator/uima/uimaj/trunk
-</pre>
+<longquote><code>% svn checkout \<br/>
+ https://svn.apache.org/repos/asf/incubator/uima/uimaj/trunk</code></longquote>
</subsection>
<subsection name="Checking Out Code using Eclipse" id="checkout.using.eclipse">
@@ -194,9 +189,9 @@
description, or your initials, e.g.
UIMA-104.clr.patch
</p>
-<pre>
+<longquote><pre>
% svn diff > UIMA-104.clr.patch
-</pre>
+</pre></longquote>
</subsection>
<subsection name="Committing changes to subversion" id="committing.changes">
@@ -210,19 +205,20 @@
<p>
Once your password is set, you can use a command like this to commit:
</p>
-<pre>
-$> svn commit --username your-username
-Authentication realm: <https://svn.apache.org:443> ASF Committers
-Password for 'your-username': your-password
-</pre>
+<longquote><pre>
+$> svn commit --username your-username \
+ Authentication realm: <https://svn.apache.org:443> \
+ ASF Committers Password for 'your-username': your-password
+</pre></longquote>
<p>You can also pass your password on the command line directly, but
this is a security problem on multiuser unix computers (the command line
arguments are available via the ps command). Here is the command if you
are Windows or a single user unix computer:
</p>
-<pre>
-$> svn commit --username your-username --password your-password
-</pre>
+<longquote><pre>
+$> svn commit --username your-username \
+ --password your-password
+</pre></longquote>
<p>Remember to replace 'your-username' and 'your-password' with
your actual username and password on svn.apache.org.
</p>
@@ -230,9 +226,10 @@
Please also add to your commit statement an appropriate message that explains the changes you did.
You can add a message when adding <code>--message</code> to your commit statement:
</p>
-<pre>
-$> svn commit --username your-username --password your-password --message your-message
-</pre>
+<longquote><pre>
+$> svn commit --username your-username \
+ --password your-password --message your-message
+</pre></longquote>
<p>
Please always enter the JIRA issue key and additionally the JIRA issue link
to the commit message. The issue key (e.g., UIMA-555) is important so that the JIRA SVN plugin can detect the
@@ -257,25 +254,26 @@
</p>
<subsection name="Building from the command line" id="building.command.line">
<p>
-<pre>
+<longquote><pre>
$> cd uimaj
$> mvn install
-</pre>
+</pre></longquote>
</p>
<p>
The first time you try this, you will probably get an error that <code>javax:activation:activation:jar:1.0.2</code> is not found. To resolve this,
download <code>activation.jar</code> from <a class="external" rel="nofollow" href="http://java.sun.com/products/archive/javabeans/jaf102.html">
http://java.sun.com/products/archive/javabeans/jaf102.html
</a> and execute the command:
-<pre>
-$> mvn install:install-file -DgroupId=javax.activation -DartifactId=activation -Dversion=1.0.2
- \ -Dpackaging=jar -Dfile=/path/to/file/activation.jar
-</pre>
-
+<longquote><pre>
+$> mvn install:install-file \
+ -DgroupId=javax.activation \
+ -DartifactId=activation \
+ -Dversion=1.0.2 \
+ -Dpackaging=jar \
+ -Dfile=/path/to/file/activation.jar
+</pre></longquote>
then re-run the UIMA build with the command:
-<pre>
-$> mvn install
-</pre>
+<longquote><pre>$> mvn install</pre></longquote>
</p>
<p>
This should build all of the jars and run the unit tests. Each jar will be located under the <code>target</code> subdirectory of its project, for example <code>uimaj-core/target/uima-core.jar</code>.
@@ -289,32 +287,43 @@
<subsection name="Building from Eclipse" id="building.eclipse">
<p>
<ol>
- <li>First, follow all the steps under "Building from the command line, above." You
- will only need to do this once.</li>
- <li>(Optional) If you want a new workspace for the maven work, start Eclipse and create a new workspace. </li>
- <li>In a command window, execute
- <br/>
- <code>mvn -Declipse.workspace=<eclipse workspace dir> eclipse:add-maven-repo</code>
- <br/> This adds a maven repository to your machine (On Windows, under documents & settings / .m2 /
- repository), and sets up an Eclipse Java Build Path variable to reference it.</li>
- <li>Use Eclipse's SVN Repository explorer to checkout all the projects under uimaj/trunk. Tell it to create
- new Java projects for these.</li>
- <li>
+ <li><p>First, follow all the steps under "Building from the command line, above." You
+ will only need to do this once.</p></li>
+ <li><p>(Optional) If you want a new workspace for the maven work, start Eclipse and create a new workspace. </p></li>
+ <li><p>In a command window, execute
+ <blockquote>
+ <pre>
+mvn -Declipse.workspace=<eclipse workspace dir> \
+ eclipse:add-maven-repo</pre>
+ </blockquote>
+ This adds a maven repository to your machine (On Windows, under documents & settings / .m2 /
+ repository), and sets up an Eclipse Java Build Path variable to reference it.</p></li>
+ <li><p>Use Eclipse's SVN Repository explorer to checkout all the projects under uimaj/trunk. Tell it to create
+ new Java projects for these.</p></li>
+ <li><p>
<code>cd uimaj</code> to switch to the Eclipse workspace for the uimaj project itself is (it has the top level
POM), and run the command:
- <br/>
- <code>mvn eclipse:eclipse</code>
- <br/> If you notice error messages that components need to be downloaded from the maven repository, it might
+ <blockquote><code>mvn eclipse:eclipse</code></blockquote>
+ </p><p>
+ If you haven't run the "install" using maven (because you forgot to follow all the steps under
+ "Building from the command line, above"), you should do the command
+ <code>mvn install eclipse:eclipse</code>. The "install" argument builds UIMA using maven,
+ before the eclipse:eclipse goal is run. This
+ is needed for the Eclipse Plugins that are part of UIMA - these projects have their
+ "MANIFEST.MF" file built by maven from the information in the maven POMs. This step
+ may take a few minutes because the "install" lifecycle includes running the unit tests.
+ </p><p>
+ If you notice error messages that components need to be downloaded from the maven repository, it might
tell you to redo the command using the
- <code>-DdownloadSources=true</code> parameter in order to check remote repositories for sources.</li>
- <li>Return to Eclipse, and if needed, select all the projects and push F5 to "refresh" them (because the
+ <code>-DdownloadSources=true</code> parameter in order to check remote repositories for sources.</p></li>
+ <li><p>Return to Eclipse, and if needed, select all the projects and push F5 to "refresh" them (because the
previous command changed the .project and .classpath files). You can set your workspace to automatically
- refresh - in which case skip this step.</li>
- <li>The projects should now compile without errors, and have build paths which reference copies of things in
- your local maven repository.</li>
- <li>You can run the unit tests in Eclipse by right-clicking on a folder (for example
+ refresh - in which case skip this step.</p></li>
+ <li><p>The projects should now compile without errors, and have build paths which reference copies of things in
+ your local maven repository.</p></li>
+ <li><p>You can run the unit tests in Eclipse by right-clicking on a folder (for example
<code>uimaj-core/src/test/java</code>) and selecting Run As -> JUnit Test. This will run all tests
- under that folder.</li>
+ under that folder.</p></li>
</ol>
</p>
</subsection>
@@ -330,7 +339,7 @@
If not using Eclipse, you can use <code>grep</code> to accomplish the same thing.
</p>
-<p>You can bypass the tests by doing mvn -Dmaven.test.skip=true install. But please do this only
+<p>You can bypass the tests by doing mvn -Dmaven.test.skip install. But please do this only
after you've run without it and have verified the tests results.</p>
</subsection>
@@ -340,8 +349,11 @@
version 3.3 or later installed, and you have to indicate to maven where it is installed.
In the examples below, this is shown as c:/your/path/to/eclipse.
Note that you can type the slashes '/' as backslashes '\' in Windows -- it doesn't matter
- (both work). The path should be to an directory named "eclipse" containing as subdirectories folders such as
- "plugins" and "features"</p>
+ (both work). The path should be to an directory (which, by default is
+ often named "eclipse" but can be named anything) containing the eclipse
+ executable, and the subdirectory folders for Eclipse such as "plugins"
+ and "features".
+ </p>
<p>
You can do this in one of 3 ways.
</p>
@@ -351,11 +363,12 @@
useful for other things as well, such as specifying upload servers. The file contents that
you need to specify the Eclipse location looks like this:
</p>
- <pre>
+<pre>
<settings xmlns="http://maven.apache.org/POM/4.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
- xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
- http://maven.apache.org/xsd/settings-1.0.0.xsd">
+ xsi:schemaLocation=
+ "http://maven.apache.org/POM/4.0.0
+ http://maven.apache.org/xsd/settings-1.0.0.xsd">
<profiles>
<profile>
<id>local-build-configuration</id>
@@ -363,29 +376,33 @@
<activeByDefault>true</activeByDefault>
</activation>
<properties>
- <uima-maven-build-eclipse-home>c:/your/path/to/eclipse</uima-maven-build-eclipse-home>
+ <uima-maven-build-eclipse-home>
+ c:/your/path/to/eclipse
+ </uima-maven-build-eclipse-home>
</properties>
</profile>
</profiles>
<activeProfiles>
- <activeProfile>local-build-configuration</activeProfile>
+ <activeProfile>
+ local-build-configuration
+ </activeProfile>
</activeProfiles>
</settings>
</pre>
<p>The second way to do this is to set an environment variable. Here's an example in Windows:</p>
- <pre>set ECLIPSE_HOME=c:/your/path/to/eclipse</pre>
+ <longquote><code>set ECLIPSE_HOME=c:/your/path/to/eclipse</code></longquote>
<p>The third way is to pass a command line argument to the maven command below, which looks like this:</p>
- <pre>-Duima-maven-build-eclipse-home=c:/your/path/to/eclipse</pre>
+ <longquote><code>-Duima-maven-build-eclipse-home=c:/your/path/to/eclipse</code></longquote>
<p>
To build a distribution, first do a build as described in "Building from the command line".
Then (assuming you set up the Eclipse path using one of the first 2 methods, execute the following:
-<pre>
+<longquote><pre>
$>cd ../uimaj-distr
$>mvn assembly:assembly
-</pre>
+</pre></longquote>
This will build the javadocs and the manual (using docbooks, as described below), will create the
Eclipse update site for the Eclipse plugins, and will create