You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@river.apache.org by bu...@apache.org on 2010/11/09 16:16:41 UTC
svn commit: r778973 -
/websites/staging/river/trunk/content/building-river.html
Author: buildbot
Date: Tue Nov 9 15:16:41 2010
New Revision: 778973
URL: http://svn.apache.org/viewvc?rev=778973&view=rev
Log:
Staging update by buildbot
Modified:
websites/staging/river/trunk/content/building-river.html
Modified: websites/staging/river/trunk/content/building-river.html
URL: http://svn.apache.org/viewvc/websites/staging/river/trunk/content/building-river.html?rev=778973&r1=778972&r2=778973&view=diff
==============================================================================
--- websites/staging/river/trunk/content/building-river.html (original)
+++ websites/staging/river/trunk/content/building-river.html Tue Nov 9 15:16:41 2010
@@ -70,7 +70,21 @@
<div class="wiki-content">
<h1 id="building_river">Building River</h1>
<p>Before you can start building River a word of warning;</p>
-<p><strong>The build process does not place nicely if you have spaces in your path names</strong></p>
+<h2 id="warning">Warning</h2>
+<p>The build process does not place nicely if you have spaces in your path names. This includes the install path of the JDK.<br />
+</p>
+<p>This can be circumvented, at least on a Windows/Cygwin by using the first 6 characters of the name with a space in, and postfixing a tilde and the number 1.</p>
+<p>For example:</p>
+<div class="codehilite"><pre><span class="n">C:</span><span class="o">\</span><span class="n">Program</span> <span class="n">Files</span>
+</pre></div>
+
+
+<p>Would become:</p>
+<div class="codehilite"><pre><span class="n">C:</span><span class="o">\</span><span class="n">Progra</span><span class="o">~</span><span class="mi">1</span>
+</pre></div>
+
+
+<p>If the first six characters of your path name are not a unique name, for example if you have the two paths "C:Program Files" and "C:Program Something Else" then the number after the tilde may well be different. It is suggested that you experiment using the Windows command shell to establish the correct 'tilde plus number' name for your path.</p>
<p>So Windows users please be particular aware. Also, where path separators are specified colons (:) should be used in preference to semi-colons (;) even on Windows.</p>
<h2 id="check_out_the_code">Check out the code</h2>
<p>See <a href="source-code.html">this page</a> on how to check out the source code.</p>
@@ -86,7 +100,7 @@
<h2 id="testing_river">Testing River</h2>
<p>This build process runs the (limited) suite of unit tests that comes with River. River is tested predominantly by using <a href="http://openjdk.java.net/jtreg/">jtreg</a>.</p>
<h3 id="using_the_ant_script">Using the Ant script</h3>
-<p>The QA tests can also be run from the Ant script.</p>
+<p>The QA tests can also be run from the Ant script. You must make sure the Ant you are using is using the correct JDK. You can run "ant diagnostics" in the project directory to find out which JVM Ant is using.</p>
<p>Make sure that you have the following in your build.properties file.</p>
<div class="codehilite"><pre><span class="n">river</span><span class="o">.</span><span class="n">home</span><span class="o">=</span><span class="nv">$RIVER_HOME</span>
<span class="n">jtreg</span><span class="o">.</span><span class="n">home</span><span class="o">=</span><span class="sr">/path/</span><span class="n">to</span><span class="sr">/jtreg/i</span><span class="n">nstall</span>
@@ -101,7 +115,145 @@
</pre></div>
-<p>The specific tests and categories of test which are run is set by <strong>doing something which I can't remember</strong>.</p>
+<p>Running the entire QA suite tasks a significant portion of time; currently around the 17 hour mark. It is therefore useful to be able to specify a subset of categories or even specific tests to run. When running the QA tests with Ant, this is done by including the following in the Ant build.properties file.</p>
+<div class="codehilite"><pre><span class="c1"># runs a specified category</span>
+<span class="c1"># e.g. run.categories=lookupservice</span>
+<span class="n">run</span><span class="o">.</span><span class="n">categories</span><span class="o">=</span><span class="n">name_of_category</span>
+
+<span class="c1"># runs a specified test</span>
+<span class="c1"># e.g. run.tests=com/sun/jini/test/spec/constraint/coreconstraint/PrincipalElementsTest.td</span>
+<span class="n">run</span><span class="o">.</span><span class="n">tests</span><span class="o">=</span><span class="n">path</span><span class="sr">/to/</span><span class="n">test</span><span class="o">/</span><span class="n">TestName</span><span class="o">.</span><span class="n">td</span>
+</pre></div>
+
+
+<p>The td files can be found in;</p>
+<div class="codehilite"><pre><span class="nv">$RIVER_HOME</span><span class="sr">/qa/s</span><span class="n">rc</span><span class="o">/**</span>
+</pre></div>
+
+
+<p>The test categories are;</p>
+<ol>
+<li>activation</li>
+<li>activation_spec</li>
+<li>allgroups</li>
+<li>basicinvocationdispatcher</li>
+<li>basicinvocationdispatcher_spec</li>
+<li>basicinvocationhandler</li>
+<li>basicinvocationhandler_spec</li>
+<li>basicobjectendpoint</li>
+<li>basicobjectendpoint_spec</li>
+<li>config</li>
+<li>config_spec</li>
+<li>constraint</li>
+<li>constraint_spec</li>
+<li>coreconstraint</li>
+<li>coreconstraint_spec</li>
+<li>discardproblem</li>
+<li>discoverymanager</li>
+<li>discoverymanager_impl</li>
+<li>discoverymanager_spec</li>
+<li>discoveryproviders</li>
+<li>discoveryproviders_impl</li>
+<li>discoveryservice</li>
+<li>discoveryservice_impl</li>
+<li>discoveryservice_spec</li>
+<li>discoveryserviceevent</li>
+<li>discoveryservicelease</li>
+<li>end2end</li>
+<li>end2end_impl</li>
+<li>eventmailbox</li>
+<li>eventmailbox_impl</li>
+<li>eventmailbox_spec</li>
+<li>export</li>
+<li>export_spec</li>
+<li>fiddleradmin</li>
+<li>fiddlerfiddleradmin</li>
+<li>fiddlerjoinadmin</li>
+<li>id</li>
+<li>id_spec</li>
+<li>iiop</li>
+<li>iiop_spec</li>
+<li>impllocatordiscovery</li>
+<li>impllookupdiscovery</li>
+<li>implservicediscovery</li>
+<li>implservicediscoveryevent</li>
+<li>io</li>
+<li>io_spec</li>
+<li>javaspace</li>
+<li>javaspace05_conformance</li>
+<li>javaspace_conformance</li>
+<li>javaspace_impl</li>
+<li>javaspace_impl_admin</li>
+<li>javaspace_impl_api</li>
+<li>javaspace_impl_javaspace05</li>
+<li>javaspace_impl_leasing</li>
+<li>javaspace_impl_matching</li>
+<li>javaspace_impl_notify</li>
+<li>javaspace_impl_transaction</li>
+<li>javaspace_spec</li>
+<li>jeri</li>
+<li>jeri_spec</li>
+<li>joinmanager</li>
+<li>joinmanager_impl</li>
+<li>joinmanager_spec</li>
+<li>jrmp</li>
+<li>jrmp_spec</li>
+<li>loader</li>
+<li>loader_spec</li>
+<li>locatordiscovery</li>
+<li>locatordiscovery_impl</li>
+<li>locatordiscovery_spec</li>
+<li>lookupdiscovery</li>
+<li>lookupdiscovery_impl</li>
+<li>lookupdiscovery_spec</li>
+<li>lookupservice</li>
+<li>lookupservice_impl</li>
+<li>lookupservice_spec</li>
+<li>policyprovider</li>
+<li>policyprovider_spec</li>
+<li>proxytrust</li>
+<li>proxytrust_spec</li>
+<li>reliability</li>
+<li>renewalmanager</li>
+<li>renewalmanager_spec</li>
+<li>renewalservice</li>
+<li>renewalservice_impl</li>
+<li>renewalservice_spec</li>
+<li>scalability</li>
+<li>security</li>
+<li>security_spec</li>
+<li>servicediscovery</li>
+<li>servicediscovery_impl</li>
+<li>servicediscovery_spec</li>
+<li>servicediscoverycache</li>
+<li>servicediscoverydiscovery</li>
+<li>servicediscoveryevent</li>
+<li>servicediscoverylookup</li>
+<li>snapshot</li>
+<li>spec</li>
+<li>speclocatordiscovery</li>
+<li>speclookupdiscovery</li>
+<li>specservicediscovery</li>
+<li>specservicediscoverycache</li>
+<li>specservicediscoverydiscovery</li>
+<li>specservicediscoveryevent</li>
+<li>specservicediscoverylookup</li>
+<li>start</li>
+<li>start_impl</li>
+<li>stress</li>
+<li>test_set00</li>
+<li>test_set01</li>
+<li>test_set02</li>
+<li>test_set03</li>
+<li>test_set04</li>
+<li>thread</li>
+<li>thread_impl</li>
+<li>txnmanager</li>
+<li>txnmanager_impl</li>
+<li>txnmanager_spec</li>
+<li>url</li>
+<li>url_spec</li>
+</ol>
<h3 id="using_jtreg_directly">Using jtreg directly</h3>
<p>You must first download and install jtreg following the instructions on their site.</p>
<p>Execute the following:</p>
@@ -131,9 +283,6 @@
<span class="o">-</span><span class="n">Djtlib</span><span class="o">.</span><span class="n">tmp</span><span class="o">=.</span><span class="sr">/qa/</span><span class="n">jtreg</span><span class="o">/</span><span class="n">JTlib</span><span class="o">-</span><span class="n">tmp</span> <span class="o">\</span>
<span class="o">.</span><span class="sr">/qa/</span><span class="n">jtreg</span><span class="o">/</span>
</pre></div>
-
-
-<p>The specific tests and categories of test which are run is set by <strong>doing something which I can't remember</strong>.</p>
</div>
</td>
<td valign="top">