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 2015/09/08 08:48:53 UTC
svn commit: r964717 [1/3] - in /websites/staging/river/trunk/content: ./ doc/
Author: buildbot
Date: Tue Sep 8 06:48:52 2015
New Revision: 964717
Log:
Staging update by buildbot for river
Removed:
websites/staging/river/trunk/content/doc/
Modified:
websites/staging/river/trunk/content/ (props changed)
websites/staging/river/trunk/content/about.html
websites/staging/river/trunk/content/building-a-release.html
websites/staging/river/trunk/content/building-river.html
websites/staging/river/trunk/content/ci.html
websites/staging/river/trunk/content/coding.html
websites/staging/river/trunk/content/concepts.html
websites/staging/river/trunk/content/development-process.html
websites/staging/river/trunk/content/discussion-futuredirection.html
websites/staging/river/trunk/content/discussion-internet.html
websites/staging/river/trunk/content/discussion-jarpackaging.html
websites/staging/river/trunk/content/documentation.html
websites/staging/river/trunk/content/found-a-bug.html
websites/staging/river/trunk/content/generics-javaspaces.html
websites/staging/river/trunk/content/get-involved.html
websites/staging/river/trunk/content/helloworld.html
websites/staging/river/trunk/content/index.html
websites/staging/river/trunk/content/mailing-lists.html
websites/staging/river/trunk/content/maven-artifacts.html
websites/staging/river/trunk/content/networking.html
websites/staging/river/trunk/content/people.html
websites/staging/river/trunk/content/resources.html
websites/staging/river/trunk/content/roadmap.html
websites/staging/river/trunk/content/source-code.html
websites/staging/river/trunk/content/success-stories.html
websites/staging/river/trunk/content/supported-platforms.html
websites/staging/river/trunk/content/testing-categories.html
websites/staging/river/trunk/content/user-guide-basic-river-services.html
websites/staging/river/trunk/content/user-guide-glossary.html
websites/staging/river/trunk/content/user-guide-river-jar-artifacts.html
websites/staging/river/trunk/content/user-guide-socketfactories.html
websites/staging/river/trunk/content/wot.html
Propchange: websites/staging/river/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Tue Sep 8 06:48:52 2015
@@ -1 +1 @@
-1696277
+1701731
Modified: websites/staging/river/trunk/content/about.html
==============================================================================
--- websites/staging/river/trunk/content/about.html (original)
+++ websites/staging/river/trunk/content/about.html Tue Sep 8 06:48:52 2015
@@ -66,7 +66,18 @@
<tr>
<td style="overflow: hidden;" valign="top" width="100%">
<div class="wiki-content">
-<h1 id="about-apache-river">About Apache River</h1>
+<style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h1 id="about-apache-river">About Apache River<a class="headerlink" href="#about-apache-river" title="Permanent link">¶</a></h1>
<p>Welcome to Apache River, a project furthering the development
and advancement of Jini technology.</p>
<p>Jini is a service oriented architecture that defines
@@ -85,7 +96,18 @@ computing environments.</p>
<div class="navigation_top">
<div class="navigation_bottom">
<!-- sidenav -->
-<h3 id="the-foundation">The Foundation</h3>
+<style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h3 id="the-foundation">The Foundation<a class="headerlink" href="#the-foundation" title="Permanent link">¶</a></h3>
<ul>
<li><a href="http://www.apache.org">Apache</a></li>
<li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
@@ -93,7 +115,7 @@ computing environments.</p>
<li><a href="http://www.apache.org/security/">Security</a></li>
<li><a href="http://www.apache.org/foundation/how-it-works.html">How it works</a></li>
</ul>
-<h3 id="apache-river">Apache river</h3>
+<h3 id="apache-river">Apache river<a class="headerlink" href="#apache-river" title="Permanent link">¶</a></h3>
<ul>
<li><a href="downloads.html">Downloads</a></li>
<li><a href="maven-artifacts.html">Maven Artifacts</a></li>
@@ -101,7 +123,7 @@ computing environments.</p>
<li><a href="index.html">News</a></li>
<li><a href="about.html">About</a></li>
</ul>
-<h3 id="documentation">Documentation</h3>
+<h3 id="documentation">Documentation<a class="headerlink" href="#documentation" title="Permanent link">¶</a></h3>
<ul>
<li><a href="concepts.html">Concepts</a></li>
<li><a href="user-guide-basic-river-services.html">Getting started</a></li>
@@ -113,7 +135,7 @@ computing environments.</p>
<li><a href="resources.html">Resources</a></li>
<li><a href="building-a-release.html">Release</a></li>
</ul>
-<h3 id="community">Community</h3>
+<h3 id="community">Community<a class="headerlink" href="#community" title="Permanent link">¶</a></h3>
<ul>
<li><a href="get-involved.html">Get Involved</a></li>
<li>Discussion<ul>
@@ -129,7 +151,7 @@ computing environments.</p>
<li><a href="people.html">People</a></li>
<li><a href="found-a-bug.html">Found a Bug</a>?</li>
</ul>
-<h3 id="development">Development</h3>
+<h3 id="development">Development<a class="headerlink" href="#development" title="Permanent link">¶</a></h3>
<ul>
<li><a href="source-code.html">Source Code</a></li>
<li><a href="building-river.html">Building River</a></li>
@@ -139,7 +161,7 @@ computing environments.</p>
<li><a href="https://issues.apache.org/jira/browse/RIVER">Issue Tracker</a></li>
<li><a href="http://wiki.apache.org/river/">Wiki</a></li>
</ul>
-<h3 id="search">Search</h3>
+<h3 id="search">Search<a class="headerlink" href="#search" title="Permanent link">¶</a></h3>
<DIV>
<form method="get" action="http://www.google.com/search" id="search" name="search" style="font-size: 10px;">
<input type="hidden" name="sitesearch" value="river.apache.org">
Modified: websites/staging/river/trunk/content/building-a-release.html
==============================================================================
--- websites/staging/river/trunk/content/building-a-release.html (original)
+++ websites/staging/river/trunk/content/building-a-release.html Tue Sep 8 06:48:52 2015
@@ -66,21 +66,32 @@
<tr>
<td style="overflow: hidden;" valign="top" width="100%">
<div class="wiki-content">
-<h1 id="building-a-release-major-release">Building a release major release</h1>
+<style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h1 id="building-a-release-major-release">Building a release major release<a class="headerlink" href="#building-a-release-major-release" title="Permanent link">¶</a></h1>
<p>n.m n = major release number, m = minor release number</p>
-<h2 id="keys-file">KEYS file</h2>
+<h2 id="keys-file">KEYS file<a class="headerlink" href="#keys-file" title="Permanent link">¶</a></h2>
<p>Add your key to the KEYS file in the repo</p>
-<h2 id="checkout-the-source">Checkout The Source</h2>
+<h2 id="checkout-the-source">Checkout The Source<a class="headerlink" href="#checkout-the-source" title="Permanent link">¶</a></h2>
<div class="codehilite"><pre><span class="n">svn</span> <span class="n">checkout</span> <span class="n">https</span><span class="p">:</span><span class="o">//</span><span class="n">svn</span><span class="p">.</span><span class="n">apache</span><span class="p">.</span><span class="n">org</span><span class="o">/</span><span class="n">repos</span><span class="o">/</span><span class="n">asf</span><span class="o">/</span><span class="n">river</span><span class="o">/</span><span class="n">jtsk</span><span class="o">/</span><span class="n">trunk</span> <span class="n">river</span>
</pre></div>
-<h2 id="pre-release-checks">Pre release checks</h2>
+<h2 id="pre-release-checks">Pre release checks<a class="headerlink" href="#pre-release-checks" title="Permanent link">¶</a></h2>
<ul>
<li>River-trunk should run successful.</li>
<li>River-verify should run successful. (not yet?)</li>
</ul>
-<h2 id="gather-release-notes-from-jira">Gather Release Notes From Jira</h2>
+<h2 id="gather-release-notes-from-jira">Gather Release Notes From Jira<a class="headerlink" href="#gather-release-notes-from-jira" title="Permanent link">¶</a></h2>
<p>First <a href="https://issues.apache.org/jira/secure/project/ViewProject.jspa?pid=12310600">manage the versions</a> of River using Jira. Make sure there is an appropriate release that Jira issues are have been assigned to. You can then view the <a href="https://issues.apache.org/jira/browse/RIVER#selectedTab=com.atlassian.jira.plugin.system.project%3Aroadmap-panel">Roadmap</a> screen in Jira to create the release and make sure that the correct Jira issues are associated to it.</p>
<p>Move the Jira issues around appropriately, especially if you're releasing before all the issues have been resolves. In this case, you need to postpone the remaining issues until a later release.</p>
<p>You can then use Jira to generate the release notes. This is done Road Map --> Release --> Summary --> Release Notes (next to "Filters").</p>
@@ -89,34 +100,34 @@
</pre></div>
-<h2 id="update-version-numbers">Update Version Numbers</h2>
+<h2 id="update-version-numbers">Update Version Numbers<a class="headerlink" href="#update-version-numbers" title="Permanent link">¶</a></h2>
<p>There are version numbers in the following places that need to be updated with the new release number/name.</p>
<ul>
<li>com.sun.jini.constants.VersionConstants.java (SERVER_VERSION)</li>
<li>river/trunk/src-doc/static/release-notes/index.html (version number)</li>
</ul>
<p>In the above HTML page, there is also a section on "changes by component" which should also be updated. This should be easy to do by referring to the Jira-generated release notes.</p>
-<h2 id="branch-the-repository">Branch the repository</h2>
+<h2 id="branch-the-repository">Branch the repository<a class="headerlink" href="#branch-the-repository" title="Permanent link">¶</a></h2>
<div class="codehilite"><pre><span class="n">svn</span> <span class="n">cp</span> <span class="n">https</span><span class="p">:</span><span class="o">//</span><span class="n">svn</span><span class="p">.</span><span class="n">apache</span><span class="p">.</span><span class="n">org</span><span class="o">/</span><span class="n">repos</span><span class="o">/</span><span class="n">asf</span><span class="o">/</span><span class="n">river</span><span class="o">/</span><span class="n">jtsk</span><span class="o">/</span><span class="n">trunk</span> <span class="n">https</span><span class="p">:</span><span class="o">//</span><span class="n">svn</span><span class="p">.</span><span class="n">apache</span><span class="p">.</span><span class="n">org</span><span class="o">/</span><span class="n">repos</span><span class="o">/</span><span class="n">asf</span><span class="o">/</span><span class="n">river</span><span class="o">/</span><span class="n">jtsk</span><span class="o">/</span><span class="n">
branches</span><span class="o">/</span>$<span class="n">VERSION</span>
</pre></div>
-<h2 id="tag-the-repository">Tag the repository</h2>
+<h2 id="tag-the-repository">Tag the repository<a class="headerlink" href="#tag-the-repository" title="Permanent link">¶</a></h2>
<div class="codehilite"><pre><span class="n">svn</span> <span class="n">cp</span> <span class="n">https</span><span class="p">:</span><span class="o">//</span><span class="n">svn</span><span class="p">.</span><span class="n">apache</span><span class="p">.</span><span class="n">org</span><span class="o">/</span><span class="n">repos</span><span class="o">/</span><span class="n">asf</span><span class="o">/</span><span class="n">river</span><span class="o">/</span><span class="n">jtsk</span><span class="o">/</span><span class="n">trunk</span> <span class="n">https</span><span class="p">:</span><span class="o">//</span><span class="n">svn</span><span class="p">.</span><span class="n">apache</span><span class="p">.</span><span class="n">org</span><span class="o">/</span><span class="n">repos</span><span class="o">/</span><span class="n">asf</span><span class="o">/</span><span class="n">river</span><span class="o">/</span><span class="n">jtsk</span><span class="o">/</span><span class="n">
tags</span><span class="o">/</span>$<span class="n">VERSION</span>
</pre></div>
-<h2 id="build-the-release-products">Build the release products</h2>
+<h2 id="build-the-release-products">Build the release products<a class="headerlink" href="#build-the-release-products" title="Permanent link">¶</a></h2>
<div class="codehilite"><pre><span class="n">ant</span> <span class="o">-</span><span class="n">Dversion</span><span class="p">=</span>$<span class="n">VERSION</span> <span class="n">clean</span> <span class="n">release</span>
</pre></div>
-<h2 id="rat-reports">Rat Reports</h2>
+<h2 id="rat-reports">Rat Reports<a class="headerlink" href="#rat-reports" title="Permanent link">¶</a></h2>
<div class="codehilite"><pre><span class="o">./</span><span class="n">rat_reports</span><span class="p">.</span><span class="n">sh</span>
</pre></div>
-<h2 id="sign-the-release">Sign the release</h2>
+<h2 id="sign-the-release">Sign the release<a class="headerlink" href="#sign-the-release" title="Permanent link">¶</a></h2>
<ul>
<li><a href="http://www.apache.org/dev/release-signing.htm">General Apache Signing Details</a></li>
<li><a href="http://www.apache.org/dev/release-signing.html#sign-release">Release Signing Instructions</a> *See code below, link has a typo in it</li>
@@ -129,7 +140,7 @@ for f in $( ls ); do
done;</p>
</li>
</ul>
-<h2 id="test-the-release">Test the release</h2>
+<h2 id="test-the-release">Test the release<a class="headerlink" href="#test-the-release" title="Permanent link">¶</a></h2>
<div class="codehilite"><pre><span class="n">cp</span> <span class="n">dist</span><span class="o">/</span><span class="n">apache</span><span class="o">-</span><span class="n">river</span><span class="o">-</span>$<span class="n">VERSION</span><span class="p">.</span><span class="n">tar</span><span class="p">.</span><span class="n">gz</span> $<span class="n">SOMEWHERE_ELSE</span>
<span class="n">cd</span> $<span class="n">SOMEWHERE_ELSE</span>
<span class="n">tar</span> <span class="n">xvf</span> <span class="n">apache</span><span class="o">-</span><span class="n">river</span><span class="o">-</span>$<span class="n">VERSION</span><span class="p">.</span><span class="n">tar</span><span class="p">.</span><span class="n">gz</span>
@@ -138,20 +149,20 @@ done;</p>
</pre></div>
-<h2 id="upload-the-release">Upload the release</h2>
+<h2 id="upload-the-release">Upload the release<a class="headerlink" href="#upload-the-release" title="Permanent link">¶</a></h2>
<div class="codehilite"><pre><span class="n">scp</span> <span class="n">RAT</span><span class="o">*</span> <span class="n">username</span><span class="p">@</span><span class="n">people</span><span class="p">.</span><span class="n">apache</span><span class="p">.</span><span class="n">org</span><span class="p">:</span><span class="o">~/</span><span class="n">public_html</span><span class="o">/</span><span class="n">river</span><span class="o">/</span>
<span class="n">cd</span> <span class="n">dist</span>
<span class="n">scp</span> <span class="o">*</span> <span class="n">username</span><span class="p">@</span><span class="n">people</span><span class="p">.</span><span class="n">apache</span><span class="p">.</span><span class="n">org</span><span class="p">:</span><span class="o">~/</span><span class="n">public_html</span><span class="o">/</span><span class="n">river</span><span class="o">/</span>
</pre></div>
-<h2 id="allow-the-community-to-evaluate-the-release-products">Allow the community to evaluate the release products</h2>
+<h2 id="allow-the-community-to-evaluate-the-release-products">Allow the community to evaluate the release products<a class="headerlink" href="#allow-the-community-to-evaluate-the-release-products" title="Permanent link">¶</a></h2>
<div class="codehilite"><pre><span class="o">*</span> <span class="n">announce</span> <span class="n">availability</span> <span class="n">of</span> <span class="n">candidate</span> <span class="n">on</span> <span class="n">river</span><span class="o">-</span><span class="n">dev</span><span class="p">.</span>
<span class="o">*</span> <span class="n">start</span> <span class="p">[</span><span class="n">VOTE</span><span class="p">]</span> <span class="n">thread</span><span class="p">.</span>
</pre></div>
-<h2 id="publish-release-on-website">Publish release on website</h2>
+<h2 id="publish-release-on-website">Publish release on website<a class="headerlink" href="#publish-release-on-website" title="Permanent link">¶</a></h2>
<ul>
<li>checkout the site </li>
<li>Extract the javadocs from the release archive into ...</li>
@@ -165,7 +176,18 @@ done;</p>
<div class="navigation_top">
<div class="navigation_bottom">
<!-- sidenav -->
-<h3 id="the-foundation">The Foundation</h3>
+<style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h3 id="the-foundation">The Foundation<a class="headerlink" href="#the-foundation" title="Permanent link">¶</a></h3>
<ul>
<li><a href="http://www.apache.org">Apache</a></li>
<li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
@@ -173,7 +195,7 @@ done;</p>
<li><a href="http://www.apache.org/security/">Security</a></li>
<li><a href="http://www.apache.org/foundation/how-it-works.html">How it works</a></li>
</ul>
-<h3 id="apache-river">Apache river</h3>
+<h3 id="apache-river">Apache river<a class="headerlink" href="#apache-river" title="Permanent link">¶</a></h3>
<ul>
<li><a href="downloads.html">Downloads</a></li>
<li><a href="maven-artifacts.html">Maven Artifacts</a></li>
@@ -181,7 +203,7 @@ done;</p>
<li><a href="index.html">News</a></li>
<li><a href="about.html">About</a></li>
</ul>
-<h3 id="documentation">Documentation</h3>
+<h3 id="documentation">Documentation<a class="headerlink" href="#documentation" title="Permanent link">¶</a></h3>
<ul>
<li><a href="concepts.html">Concepts</a></li>
<li><a href="user-guide-basic-river-services.html">Getting started</a></li>
@@ -193,7 +215,7 @@ done;</p>
<li><a href="resources.html">Resources</a></li>
<li><a href="building-a-release.html">Release</a></li>
</ul>
-<h3 id="community">Community</h3>
+<h3 id="community">Community<a class="headerlink" href="#community" title="Permanent link">¶</a></h3>
<ul>
<li><a href="get-involved.html">Get Involved</a></li>
<li>Discussion<ul>
@@ -209,7 +231,7 @@ done;</p>
<li><a href="people.html">People</a></li>
<li><a href="found-a-bug.html">Found a Bug</a>?</li>
</ul>
-<h3 id="development">Development</h3>
+<h3 id="development">Development<a class="headerlink" href="#development" title="Permanent link">¶</a></h3>
<ul>
<li><a href="source-code.html">Source Code</a></li>
<li><a href="building-river.html">Building River</a></li>
@@ -219,7 +241,7 @@ done;</p>
<li><a href="https://issues.apache.org/jira/browse/RIVER">Issue Tracker</a></li>
<li><a href="http://wiki.apache.org/river/">Wiki</a></li>
</ul>
-<h3 id="search">Search</h3>
+<h3 id="search">Search<a class="headerlink" href="#search" title="Permanent link">¶</a></h3>
<DIV>
<form method="get" action="http://www.google.com/search" id="search" name="search" style="font-size: 10px;">
<input type="hidden" name="sitesearch" value="river.apache.org">
Modified: websites/staging/river/trunk/content/building-river.html
==============================================================================
--- websites/staging/river/trunk/content/building-river.html (original)
+++ websites/staging/river/trunk/content/building-river.html Tue Sep 8 06:48:52 2015
@@ -66,8 +66,19 @@
<tr>
<td style="overflow: hidden;" valign="top" width="100%">
<div class="wiki-content">
-<h1 id="building-river">Building River</h1>
-<h2 id="prerequisites">Prerequisites</h2>
+<style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h1 id="building-river">Building River<a class="headerlink" href="#building-river" title="Permanent link">¶</a></h1>
+<h2 id="prerequisites">Prerequisites<a class="headerlink" href="#prerequisites" title="Permanent link">¶</a></h2>
<p>In order to build river, you need the following tools:</p>
<ul>
<li>Oracle JDK 1.6</li>
@@ -75,16 +86,16 @@
</ul>
<p>The rest is included in the source archive, and in the SVN.</p>
<p>This article also describes how to setup your IDE to compile River.</p>
-<h2 id="warning-spaces-in-paths">(warning) Spaces in paths</h2>
+<h2 id="warning-spaces-in-paths">(warning) Spaces in paths<a class="headerlink" href="#warning-spaces-in-paths" title="Permanent link">¶</a></h2>
<p>The build process does not play nicely if you have spaces in your path names. This includes the install path of the JDK. </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; <code>C:\Program Files</code> would become; <code>C:\Progra~1</code></p>
<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. </p>
<p>If you are running on Windows, it is also advisable to use a forward slash '/' are the path separator. This is acceptable to both Java and Ant, and has the added benefit that the paths will be correct if you decide to run the JTREG tests (some of which require a Unix-like/Cygwin environment to run scripts in). This is particularly important for the <code>river.home</code> property which is inherited from in the <code>qa/build.xml</code> file and subsequently passed onto the various classes which make up the jtreg tests.</p>
-<h2 id="check-out-the-code">Check out the code</h2>
+<h2 id="check-out-the-code">Check out the code<a class="headerlink" href="#check-out-the-code" title="Permanent link">¶</a></h2>
<p>See <a href="source-code.html">this page</a> on how to check out the source code.</p>
-<h2 id="build-the-distribution">Build the distribution</h2>
+<h2 id="build-the-distribution">Build the distribution<a class="headerlink" href="#build-the-distribution" title="Permanent link">¶</a></h2>
<p>River can be built simply by running Ant from where you checked the code out from.</p>
<p>Assume "$RIVER_HOME" is where you have checked out the code to.</p>
<div class="codehilite"><pre><span class="n">cd</span> $<span class="n">RIVER_HOME</span>
@@ -93,15 +104,15 @@
<p>Will build all the River JARs required. You will then find them in the ${RIVER_HOME}/lib* directories.</p>
-<h2 id="setting-up-the-ide">Setting up the IDE</h2>
-<h3 id="eclipse">Eclipse</h3>
+<h2 id="setting-up-the-ide">Setting up the IDE<a class="headerlink" href="#setting-up-the-ide" title="Permanent link">¶</a></h2>
+<h3 id="eclipse">Eclipse<a class="headerlink" href="#eclipse" title="Permanent link">¶</a></h3>
<p>Create your new IDE project using your prefered method (e.g. "Import from SVN" or create a new project using existing source, etc). </p>
<p>First you will need to create a new JDK system library. The normal JDK libraries that come in Eclipse have restrictions place on the <code>rt.jar</code> file which prevents the import of some proprietary Sun classes. </p>
<p>Since River is built with Ant this isn't strictly necessary, but it is if you don't want the compiler error warnings flashing up.<br />
Currently, River should be built with JDK 6 (-source 5), so please ensure that you have this installed and your new library uses it.</p>
<p>Then you need to add the JARs in <code>$RIVER_HOME/extlibs</code> to your classpath. </p>
<p>That should everything that Eclipse needs to be happy with the River code.</p>
-<h3 id="netbeans">NetBeans</h3>
+<h3 id="netbeans">NetBeans<a class="headerlink" href="#netbeans" title="Permanent link">¶</a></h3>
<ul>
<li>Checkout the trunk.</li>
<li>In Netbeans 7.2 do: <ul>
@@ -112,12 +123,12 @@ Currently, River should be built with JD
</ul>
</li>
</ul>
-<h1 id="testing-river">Testing River</h1>
+<h1 id="testing-river">Testing River<a class="headerlink" href="#testing-river" title="Permanent link">¶</a></h1>
<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> and the QA test suite.</p>
-<h2 id="the-junit-tests">The JUnit tests</h2>
+<h2 id="the-junit-tests">The JUnit tests<a class="headerlink" href="#the-junit-tests" title="Permanent link">¶</a></h2>
<p>The JUnit tests can be found in <code>$RIVER_HOME/test/src</code> you must also add the JARs found in <code>$RIVER_HOME/test/lib</code> onto the classpath for your tests.</p>
<p>It's easiest to run these tests from your IDE. In Eclipse, for example, once <code>$RIVER_HOME/test/src</code> is set at the test source directory, right-clicking the project and hitting "Run as JUnit test" is all that is required.</p>
-<h2 id="the-qa-test-suite">The QA Test Suite</h2>
+<h2 id="the-qa-test-suite">The QA Test Suite<a class="headerlink" href="#the-qa-test-suite" title="Permanent link">¶</a></h2>
<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 which you will need to create in <code>$RIVER_HOME</code>.</p>
<div class="codehilite"><pre><span class="n">river</span><span class="p">.</span><span class="n">home</span><span class="p">=</span>$<span class="n">RIVER_HOME</span>
@@ -136,9 +147,9 @@ Currently, River should be built with JD
</pre></div>
-<h3 id="running-just-a-few-tests">Running just a few tests</h3>
+<h3 id="running-just-a-few-tests">Running just a few tests<a class="headerlink" href="#running-just-a-few-tests" title="Permanent link">¶</a></h3>
<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. </p>
-<h4 id="by-settings-in-the-properties-file">By settings in the properties file</h4>
+<h4 id="by-settings-in-the-properties-file">By settings in the properties file<a class="headerlink" href="#by-settings-in-the-properties-file" title="Permanent link">¶</a></h4>
<p>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="c"># runs a specified category</span>
<span class="c"># e.g. run.categories=lookupservice</span>
@@ -150,16 +161,16 @@ Currently, River should be built with JD
</pre></div>
-<h4 id="by-specifying-on-the-commandline">By specifying on the commandline</h4>
+<h4 id="by-specifying-on-the-commandline">By specifying on the commandline<a class="headerlink" href="#by-specifying-on-the-commandline" title="Permanent link">¶</a></h4>
<p>From the qa directory:</p>
<div class="codehilite"><pre><span class="n">ant</span> <span class="o">-</span><span class="n">Drun</span><span class="p">.</span><span class="n">tests</span><span class="p">=</span><span class="n">com</span><span class="o">/</span><span class="n">sun</span><span class="o">/</span><span class="n">jini</span><span class="o">/</span><span class="n">test</span><span class="o">/</span><span class="n">spec</span><span class="o">/</span><span class="n">constraint</span><span class="o">/</span><span class="n">coreconstraint</span><span class="o">/</span><span class="n">PrincipalElementsTest</span><span class="p">.</span><span class="n">td</span> <span class="n">run</span><span class="o">-</span><span class="n">tests</span>
</pre></div>
<p>Existing QA tests can be found in the following path; <code>$RIVER_HOME/qa/src/com/sun/jini/test/**"</code></p>
-<h3 id="categories">Categories</h3>
+<h3 id="categories">Categories<a class="headerlink" href="#categories" title="Permanent link">¶</a></h3>
<p>You can find the test categories on <a href="testing-categories.html">Test categories</a></p>
-<h2 id="jtreg-tests">JTREG tests</h2>
+<h2 id="jtreg-tests">JTREG tests<a class="headerlink" href="#jtreg-tests" title="Permanent link">¶</a></h2>
<p>You must first download and install jtreg following the instructions on their site.</p>
<p>Some of these tests are run as BASH scripts, therefore, if running the jtreg tests on Windows a Cygwin (or similar) environment is necessary.</p>
<p>The JTREG tests can then be run by execute the following:</p>
@@ -179,9 +190,9 @@ Currently, River should be built with JD
</li>
</ul>
<p>JTREG will create the directory <code>$RIVER_HOME/qa/jtreg/JTreport</code> which contains a report of the test run.</p>
-<h3 id="running-specific-jtreg-tests">Running specific JTREG tests</h3>
+<h3 id="running-specific-jtreg-tests">Running specific JTREG tests<a class="headerlink" href="#running-specific-jtreg-tests" title="Permanent link">¶</a></h3>
<p><em>todo</em></p>
-<h3 id="known-problems">Known Problems</h3>
+<h3 id="known-problems">Known Problems<a class="headerlink" href="#known-problems" title="Permanent link">¶</a></h3>
<p>There are the following known problems with the jtreg tests:</p>
<ol>
<li>Running the tests in a Windows/Cygwin environment is not 100% working yet</li>
@@ -195,7 +206,18 @@ Currently, River should be built with JD
<div class="navigation_top">
<div class="navigation_bottom">
<!-- sidenav -->
-<h3 id="the-foundation">The Foundation</h3>
+<style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h3 id="the-foundation">The Foundation<a class="headerlink" href="#the-foundation" title="Permanent link">¶</a></h3>
<ul>
<li><a href="http://www.apache.org">Apache</a></li>
<li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
@@ -203,7 +225,7 @@ Currently, River should be built with JD
<li><a href="http://www.apache.org/security/">Security</a></li>
<li><a href="http://www.apache.org/foundation/how-it-works.html">How it works</a></li>
</ul>
-<h3 id="apache-river">Apache river</h3>
+<h3 id="apache-river">Apache river<a class="headerlink" href="#apache-river" title="Permanent link">¶</a></h3>
<ul>
<li><a href="downloads.html">Downloads</a></li>
<li><a href="maven-artifacts.html">Maven Artifacts</a></li>
@@ -211,7 +233,7 @@ Currently, River should be built with JD
<li><a href="index.html">News</a></li>
<li><a href="about.html">About</a></li>
</ul>
-<h3 id="documentation">Documentation</h3>
+<h3 id="documentation">Documentation<a class="headerlink" href="#documentation" title="Permanent link">¶</a></h3>
<ul>
<li><a href="concepts.html">Concepts</a></li>
<li><a href="user-guide-basic-river-services.html">Getting started</a></li>
@@ -223,7 +245,7 @@ Currently, River should be built with JD
<li><a href="resources.html">Resources</a></li>
<li><a href="building-a-release.html">Release</a></li>
</ul>
-<h3 id="community">Community</h3>
+<h3 id="community">Community<a class="headerlink" href="#community" title="Permanent link">¶</a></h3>
<ul>
<li><a href="get-involved.html">Get Involved</a></li>
<li>Discussion<ul>
@@ -239,7 +261,7 @@ Currently, River should be built with JD
<li><a href="people.html">People</a></li>
<li><a href="found-a-bug.html">Found a Bug</a>?</li>
</ul>
-<h3 id="development">Development</h3>
+<h3 id="development">Development<a class="headerlink" href="#development" title="Permanent link">¶</a></h3>
<ul>
<li><a href="source-code.html">Source Code</a></li>
<li><a href="building-river.html">Building River</a></li>
@@ -249,7 +271,7 @@ Currently, River should be built with JD
<li><a href="https://issues.apache.org/jira/browse/RIVER">Issue Tracker</a></li>
<li><a href="http://wiki.apache.org/river/">Wiki</a></li>
</ul>
-<h3 id="search">Search</h3>
+<h3 id="search">Search<a class="headerlink" href="#search" title="Permanent link">¶</a></h3>
<DIV>
<form method="get" action="http://www.google.com/search" id="search" name="search" style="font-size: 10px;">
<input type="hidden" name="sitesearch" value="river.apache.org">
Modified: websites/staging/river/trunk/content/ci.html
==============================================================================
--- websites/staging/river/trunk/content/ci.html (original)
+++ websites/staging/river/trunk/content/ci.html Tue Sep 8 06:48:52 2015
@@ -66,10 +66,21 @@
<tr>
<td style="overflow: hidden;" valign="top" width="100%">
<div class="wiki-content">
+<style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
<p>In order to find problems early, river uses <a href="http://en.wikipedia.org/wiki/Continuous_integration">Continuous Integration</a>. </p>
<p>After changes the builds are scheduled on the <a href="https://builds.apache.org/">Apache build server</a>.</p>
<p>The following jobs are used:</p>
-<table>
+<table class="table">
<thead>
<tr>
<th>Job</th>
@@ -100,14 +111,14 @@
</tbody>
</table>
<p>For their current status, see: <a href="https://builds.apache.org/view/M-R/view/River/">https://builds.apache.org/view/M-R/view/River/</a></p>
-<h2 id="river-trunk-jobs">River-trunk jobs</h2>
+<h2 id="river-trunk-jobs">River-trunk jobs<a class="headerlink" href="#river-trunk-jobs" title="Permanent link">¶</a></h2>
<p>The River trunk build is only run on Ubuntu. The naming scheme is:
River-trunk-[jdkid]</p>
-<h2 id="river-qa-jobs">River-QA- jobs</h2>
+<h2 id="river-qa-jobs">River-QA- jobs<a class="headerlink" href="#river-qa-jobs" title="Permanent link">¶</a></h2>
<p>The River QA jobs naming scheme used is: River-QA-[platformid]-[jdkid] optional [-branchid]</p>
<p>The River-trunk-QA-* jobs, build the river-runtime and the river-qa,
and tests the river-runtime with the river-qa framework.</p>
-<h2 id="platforms-and-jdks">Platforms and Jdks</h2>
+<h2 id="platforms-and-jdks">Platforms and Jdks<a class="headerlink" href="#platforms-and-jdks" title="Permanent link">¶</a></h2>
<p>The current platforms are: Solaris, Ubuntu, Windows</p>
<p>The current jdk ids are: jdk6 jdk7</p>
<p>The ant version used is: version 1.7</p>
@@ -118,7 +129,18 @@ and tests the river-runtime with the riv
<div class="navigation_top">
<div class="navigation_bottom">
<!-- sidenav -->
-<h3 id="the-foundation">The Foundation</h3>
+<style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h3 id="the-foundation">The Foundation<a class="headerlink" href="#the-foundation" title="Permanent link">¶</a></h3>
<ul>
<li><a href="http://www.apache.org">Apache</a></li>
<li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
@@ -126,7 +148,7 @@ and tests the river-runtime with the riv
<li><a href="http://www.apache.org/security/">Security</a></li>
<li><a href="http://www.apache.org/foundation/how-it-works.html">How it works</a></li>
</ul>
-<h3 id="apache-river">Apache river</h3>
+<h3 id="apache-river">Apache river<a class="headerlink" href="#apache-river" title="Permanent link">¶</a></h3>
<ul>
<li><a href="downloads.html">Downloads</a></li>
<li><a href="maven-artifacts.html">Maven Artifacts</a></li>
@@ -134,7 +156,7 @@ and tests the river-runtime with the riv
<li><a href="index.html">News</a></li>
<li><a href="about.html">About</a></li>
</ul>
-<h3 id="documentation">Documentation</h3>
+<h3 id="documentation">Documentation<a class="headerlink" href="#documentation" title="Permanent link">¶</a></h3>
<ul>
<li><a href="concepts.html">Concepts</a></li>
<li><a href="user-guide-basic-river-services.html">Getting started</a></li>
@@ -146,7 +168,7 @@ and tests the river-runtime with the riv
<li><a href="resources.html">Resources</a></li>
<li><a href="building-a-release.html">Release</a></li>
</ul>
-<h3 id="community">Community</h3>
+<h3 id="community">Community<a class="headerlink" href="#community" title="Permanent link">¶</a></h3>
<ul>
<li><a href="get-involved.html">Get Involved</a></li>
<li>Discussion<ul>
@@ -162,7 +184,7 @@ and tests the river-runtime with the riv
<li><a href="people.html">People</a></li>
<li><a href="found-a-bug.html">Found a Bug</a>?</li>
</ul>
-<h3 id="development">Development</h3>
+<h3 id="development">Development<a class="headerlink" href="#development" title="Permanent link">¶</a></h3>
<ul>
<li><a href="source-code.html">Source Code</a></li>
<li><a href="building-river.html">Building River</a></li>
@@ -172,7 +194,7 @@ and tests the river-runtime with the riv
<li><a href="https://issues.apache.org/jira/browse/RIVER">Issue Tracker</a></li>
<li><a href="http://wiki.apache.org/river/">Wiki</a></li>
</ul>
-<h3 id="search">Search</h3>
+<h3 id="search">Search<a class="headerlink" href="#search" title="Permanent link">¶</a></h3>
<DIV>
<form method="get" action="http://www.google.com/search" id="search" name="search" style="font-size: 10px;">
<input type="hidden" name="sitesearch" value="river.apache.org">
Modified: websites/staging/river/trunk/content/coding.html
==============================================================================
--- websites/staging/river/trunk/content/coding.html (original)
+++ websites/staging/river/trunk/content/coding.html Tue Sep 8 06:48:52 2015
@@ -66,18 +66,29 @@
<tr>
<td style="overflow: hidden;" valign="top" width="100%">
<div class="wiki-content">
-<h1 id="coding-conventions">Coding conventions</h1>
-<h2 id="indentation">Indentation</h2>
+<style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h1 id="coding-conventions">Coding conventions<a class="headerlink" href="#coding-conventions" title="Permanent link">¶</a></h1>
+<h2 id="indentation">Indentation<a class="headerlink" href="#indentation" title="Permanent link">¶</a></h2>
<p>Tabs are not used. Default indentation is 4 spaces.</p>
-<h2 id="other">Other</h2>
+<h2 id="other">Other<a class="headerlink" href="#other" title="Permanent link">¶</a></h2>
<p>Contributors are advised to read <a href="http://www.oracle.com/technetwork/java/codeconv-138413.html">http://www.oracle.com/technetwork/java/codeconv-138413.html</a>
and try to adhere as much as possible to these conventions.</p>
-<h2 id="reformatting">Reformatting</h2>
+<h2 id="reformatting">Reformatting<a class="headerlink" href="#reformatting" title="Permanent link">¶</a></h2>
<p>If the reformatting involves a large part of the code,
a clearly labeled 'reformatting' commit in between is recommended.
Keeping your reformatting changes limited,
reduces the change of merging conflicts by your fellow committers.</p>
-<h2 id="older-sources">Older sources</h2>
+<h2 id="older-sources">Older sources<a class="headerlink" href="#older-sources" title="Permanent link">¶</a></h2>
<p>We do not actively search and reformat source files
that are not formatted according to this convention.</p>
<p>Older sources are best viewed with tab stops at 8 space
@@ -89,7 +100,18 @@ intervals.</p>
<div class="navigation_top">
<div class="navigation_bottom">
<!-- sidenav -->
-<h3 id="the-foundation">The Foundation</h3>
+<style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h3 id="the-foundation">The Foundation<a class="headerlink" href="#the-foundation" title="Permanent link">¶</a></h3>
<ul>
<li><a href="http://www.apache.org">Apache</a></li>
<li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
@@ -97,7 +119,7 @@ intervals.</p>
<li><a href="http://www.apache.org/security/">Security</a></li>
<li><a href="http://www.apache.org/foundation/how-it-works.html">How it works</a></li>
</ul>
-<h3 id="apache-river">Apache river</h3>
+<h3 id="apache-river">Apache river<a class="headerlink" href="#apache-river" title="Permanent link">¶</a></h3>
<ul>
<li><a href="downloads.html">Downloads</a></li>
<li><a href="maven-artifacts.html">Maven Artifacts</a></li>
@@ -105,7 +127,7 @@ intervals.</p>
<li><a href="index.html">News</a></li>
<li><a href="about.html">About</a></li>
</ul>
-<h3 id="documentation">Documentation</h3>
+<h3 id="documentation">Documentation<a class="headerlink" href="#documentation" title="Permanent link">¶</a></h3>
<ul>
<li><a href="concepts.html">Concepts</a></li>
<li><a href="user-guide-basic-river-services.html">Getting started</a></li>
@@ -117,7 +139,7 @@ intervals.</p>
<li><a href="resources.html">Resources</a></li>
<li><a href="building-a-release.html">Release</a></li>
</ul>
-<h3 id="community">Community</h3>
+<h3 id="community">Community<a class="headerlink" href="#community" title="Permanent link">¶</a></h3>
<ul>
<li><a href="get-involved.html">Get Involved</a></li>
<li>Discussion<ul>
@@ -133,7 +155,7 @@ intervals.</p>
<li><a href="people.html">People</a></li>
<li><a href="found-a-bug.html">Found a Bug</a>?</li>
</ul>
-<h3 id="development">Development</h3>
+<h3 id="development">Development<a class="headerlink" href="#development" title="Permanent link">¶</a></h3>
<ul>
<li><a href="source-code.html">Source Code</a></li>
<li><a href="building-river.html">Building River</a></li>
@@ -143,7 +165,7 @@ intervals.</p>
<li><a href="https://issues.apache.org/jira/browse/RIVER">Issue Tracker</a></li>
<li><a href="http://wiki.apache.org/river/">Wiki</a></li>
</ul>
-<h3 id="search">Search</h3>
+<h3 id="search">Search<a class="headerlink" href="#search" title="Permanent link">¶</a></h3>
<DIV>
<form method="get" action="http://www.google.com/search" id="search" name="search" style="font-size: 10px;">
<input type="hidden" name="sitesearch" value="river.apache.org">
Modified: websites/staging/river/trunk/content/concepts.html
==============================================================================
--- websites/staging/river/trunk/content/concepts.html (original)
+++ websites/staging/river/trunk/content/concepts.html Tue Sep 8 06:48:52 2015
@@ -66,14 +66,25 @@
<tr>
<td style="overflow: hidden;" valign="top" width="100%">
<div class="wiki-content">
-<h1 id="river">River</h1>
+<style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h1 id="river">River<a class="headerlink" href="#river" title="Permanent link">¶</a></h1>
<p>River is a toolkit to build distributed systems with.
The basic communication between client and service is based on RPC.</p>
-<h1 id="communication">Communication</h1>
+<h1 id="communication">Communication<a class="headerlink" href="#communication" title="Permanent link">¶</a></h1>
<p>Client and service communicate with a protocol called JERI.
There are JERI implementations for plain-TCP, plain-SSL, HTTP, HTTPS and Kerberos-TCP.
For compatibility with RMI there is also a JRMP transport.</p>
-<h1 id="from-small-to-big">From small to big</h1>
+<h1 id="from-small-to-big">From small to big<a class="headerlink" href="#from-small-to-big" title="Permanent link">¶</a></h1>
<p>The smallest river system is comprised of a service and a client.
They only make use of JERI to communicate. No dynamic discovery is possible.</p>
<p>The next system in size is a combination of a service, client and a registry.
@@ -81,9 +92,9 @@ This allows for automatic discovery of c
The VM hosting the service registers the service in the registry.</p>
<p>For a system that also provides for ondemand distribution of compiled code, you will need a service,
client, registry and class-server.</p>
-<h1 id="basic-services">Basic services</h1>
+<h1 id="basic-services">Basic services<a class="headerlink" href="#basic-services" title="Permanent link">¶</a></h1>
<p>There are several basic services. For locking, distributed events, leasing, transactions.</p>
-<h1 id="extended-services">Extended services</h1>
+<h1 id="extended-services">Extended services<a class="headerlink" href="#extended-services" title="Permanent link">¶</a></h1>
<p>River has an implementation of 'Tuple spaces' called JavaSpaces.</p>
</div>
</td>
@@ -92,7 +103,18 @@ client, registry and class-server.</p>
<div class="navigation_top">
<div class="navigation_bottom">
<!-- sidenav -->
-<h3 id="the-foundation">The Foundation</h3>
+<style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h3 id="the-foundation">The Foundation<a class="headerlink" href="#the-foundation" title="Permanent link">¶</a></h3>
<ul>
<li><a href="http://www.apache.org">Apache</a></li>
<li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
@@ -100,7 +122,7 @@ client, registry and class-server.</p>
<li><a href="http://www.apache.org/security/">Security</a></li>
<li><a href="http://www.apache.org/foundation/how-it-works.html">How it works</a></li>
</ul>
-<h3 id="apache-river">Apache river</h3>
+<h3 id="apache-river">Apache river<a class="headerlink" href="#apache-river" title="Permanent link">¶</a></h3>
<ul>
<li><a href="downloads.html">Downloads</a></li>
<li><a href="maven-artifacts.html">Maven Artifacts</a></li>
@@ -108,7 +130,7 @@ client, registry and class-server.</p>
<li><a href="index.html">News</a></li>
<li><a href="about.html">About</a></li>
</ul>
-<h3 id="documentation">Documentation</h3>
+<h3 id="documentation">Documentation<a class="headerlink" href="#documentation" title="Permanent link">¶</a></h3>
<ul>
<li><a href="concepts.html">Concepts</a></li>
<li><a href="user-guide-basic-river-services.html">Getting started</a></li>
@@ -120,7 +142,7 @@ client, registry and class-server.</p>
<li><a href="resources.html">Resources</a></li>
<li><a href="building-a-release.html">Release</a></li>
</ul>
-<h3 id="community">Community</h3>
+<h3 id="community">Community<a class="headerlink" href="#community" title="Permanent link">¶</a></h3>
<ul>
<li><a href="get-involved.html">Get Involved</a></li>
<li>Discussion<ul>
@@ -136,7 +158,7 @@ client, registry and class-server.</p>
<li><a href="people.html">People</a></li>
<li><a href="found-a-bug.html">Found a Bug</a>?</li>
</ul>
-<h3 id="development">Development</h3>
+<h3 id="development">Development<a class="headerlink" href="#development" title="Permanent link">¶</a></h3>
<ul>
<li><a href="source-code.html">Source Code</a></li>
<li><a href="building-river.html">Building River</a></li>
@@ -146,7 +168,7 @@ client, registry and class-server.</p>
<li><a href="https://issues.apache.org/jira/browse/RIVER">Issue Tracker</a></li>
<li><a href="http://wiki.apache.org/river/">Wiki</a></li>
</ul>
-<h3 id="search">Search</h3>
+<h3 id="search">Search<a class="headerlink" href="#search" title="Permanent link">¶</a></h3>
<DIV>
<form method="get" action="http://www.google.com/search" id="search" name="search" style="font-size: 10px;">
<input type="hidden" name="sitesearch" value="river.apache.org">
Modified: websites/staging/river/trunk/content/development-process.html
==============================================================================
--- websites/staging/river/trunk/content/development-process.html (original)
+++ websites/staging/river/trunk/content/development-process.html Tue Sep 8 06:48:52 2015
@@ -66,6 +66,17 @@
<tr>
<td style="overflow: hidden;" valign="top" width="100%">
<div class="wiki-content">
+<style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
<div class="toc">
<ul>
<li><a href="#river-development-process">River Development Process</a><ul>
@@ -80,10 +91,10 @@
</li>
</ul>
</div>
-<h1 id="river-development-process">River Development Process</h1>
-<h2 id="river-build-server">River build server</h2>
+<h1 id="river-development-process">River Development Process<a class="headerlink" href="#river-development-process" title="Permanent link">¶</a></h1>
+<h2 id="river-build-server">River build server<a class="headerlink" href="#river-build-server" title="Permanent link">¶</a></h2>
<p>River is built on the Apache Hudson server. The projects can be found <a href="https://hudson.apache.org/hudson/view/M-R/view/River/">here</a>. More on this process: <a href="ci.html">Continuous Integration</a></p>
-<h2 id="tracking-issues-and-changes">Tracking issues and changes</h2>
+<h2 id="tracking-issues-and-changes">Tracking issues and changes<a class="headerlink" href="#tracking-issues-and-changes" title="Permanent link">¶</a></h2>
<ul>
<li>
<p>A JIRA issue is required for any substantive change.
@@ -97,7 +108,7 @@ In order to keep the list of JIRA issues
The preferred place of discussion on issues is the river-dev mail list. A link to the beginning of the mail thread on the issue should be placed in the JIRA issue so that users looking through JIRA can easily view the thread of discussion on an issue. Please keep the Subject line the same so that the email thread hangs together. It's also recommended that a summary/conclusion on the thread be recorded in the JIRA issue itself.</p>
</li>
</ul>
-<h2 id="handling-security-related-issues">Handling Security -related Issues</h2>
+<h2 id="handling-security-related-issues">Handling Security -related Issues<a class="headerlink" href="#handling-security-related-issues" title="Permanent link">¶</a></h2>
<p>There are three options associated with the "Security Level" field in the JIRA instance:
<em> "None"
</em> "Security risk, visible to committers" - only committers have access to the issue with this option set
@@ -105,7 +116,7 @@ The preferred place of discussion on iss
<p>When a potential security -related issue is identified in the River sourcebase, initial discussion on it should occur on the private PPMC list. If the person(s) who identified the issue are not on the PPMC, they should be included in the discussion.</p>
<p>If the issue is acknowledged as a valid security issue, a JIRA issue needs to be created with the "Security Level" field marked to "Security risk, visible to committers".</p>
<p>As soon as appropriate (for example, when the impact is understood and/or there is a resolution/fix developed), the "Security Level" should be changed to "Security risk, visible to anyone" and an explanation/discussion should occur in the broader River community on the river-dev list.</p>
-<h2 id="code-reviews">Code Reviews</h2>
+<h2 id="code-reviews">Code Reviews<a class="headerlink" href="#code-reviews" title="Permanent link">¶</a></h2>
<ul>
<li>
<p>for public API changes:
@@ -116,9 +127,9 @@ The preferred place of discussion on iss
<a href="http://apache.org/foundation/glossary.html#CommitThenReview">CTR</a> Although CTR is what is specified, developers should feel comfortable requesting the list for peer review before committing.</p>
</li>
</ul>
-<h2 id="testing">Testing</h2>
+<h2 id="testing">Testing<a class="headerlink" href="#testing" title="Permanent link">¶</a></h2>
<p>Developing test cases and running test suites are desired but not required prior to an integration. If unit tests are created for a change, the developer is encouraged to add them to the JIRA issue for sharing.</p>
-<h2 id="version-numbering">Version Numbering</h2>
+<h2 id="version-numbering">Version Numbering<a class="headerlink" href="#version-numbering" title="Permanent link">¶</a></h2>
<p>Each Apache River deliverable has a version number of:</p>
<p><code>m.n.r</code></p>
<ul>
@@ -127,12 +138,12 @@ The preferred place of discussion on iss
<li><code>r</code> = maintenance version</li>
</ul>
<p>The major version number will in general only be increased in case of major changes that might introduce compatibility problems or represent some fundamental improvements. The minor versions reflect the various feature releases, the last part of the version number reflects the maintenance release.</p>
-<h2 id="branching-policy">Branching Policy</h2>
+<h2 id="branching-policy">Branching Policy<a class="headerlink" href="#branching-policy" title="Permanent link">¶</a></h2>
<p>Ongoing development for the next release takes place in the <code>/trunk</code>. Once feature complete for a (non maintenance) release the trunk is branched into <code>/branches/<m.n></code> which in general also reflects the moment a release candidate is presented to the public in a fairly short period of time. Ongoing development continues in the <code>/trunk</code>, issues found against the release candidate will be fixed in <code>/branches/<m.n></code> and likely merged into the <code>/trunk</code>.</p>
<p>Once a release candidate is ready for a first customer release <code>/branches/<m.n></code> is branched into <code>/tags/<m.n>.0</code>. When support is required for a particular release <code>m.n</code>, the development for a fix-release is conducted in <code>/branches/<m.n></code>. When a bug-fix release is ready it is branched into <code>/tags/<m.n.r></code> where <code>r</code> is a positive number and increased for each maintenance release.</p>
<p>Although ongoing development should take place in <code>/trunk</code>, there is a <code>/skunk</code> branch that can be utilized for 'experimental' work that must not disturb the <code>/trunk</code>, that needs to be visible to others and/or might require participation of others. In general the lifetime of such branch should be short to give it a chance of successful integration into the <code>/trunk</code> when the 'experiment' has been found valuable.</p>
<p><em>Summarized</em></p>
-<table>
+<table class="table">
<thead>
<tr>
<th>branch</th>
@@ -189,7 +200,18 @@ The preferred place of discussion on iss
<div class="navigation_top">
<div class="navigation_bottom">
<!-- sidenav -->
-<h3 id="the-foundation">The Foundation</h3>
+<style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h3 id="the-foundation">The Foundation<a class="headerlink" href="#the-foundation" title="Permanent link">¶</a></h3>
<ul>
<li><a href="http://www.apache.org">Apache</a></li>
<li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
@@ -197,7 +219,7 @@ The preferred place of discussion on iss
<li><a href="http://www.apache.org/security/">Security</a></li>
<li><a href="http://www.apache.org/foundation/how-it-works.html">How it works</a></li>
</ul>
-<h3 id="apache-river">Apache river</h3>
+<h3 id="apache-river">Apache river<a class="headerlink" href="#apache-river" title="Permanent link">¶</a></h3>
<ul>
<li><a href="downloads.html">Downloads</a></li>
<li><a href="maven-artifacts.html">Maven Artifacts</a></li>
@@ -205,7 +227,7 @@ The preferred place of discussion on iss
<li><a href="index.html">News</a></li>
<li><a href="about.html">About</a></li>
</ul>
-<h3 id="documentation">Documentation</h3>
+<h3 id="documentation">Documentation<a class="headerlink" href="#documentation" title="Permanent link">¶</a></h3>
<ul>
<li><a href="concepts.html">Concepts</a></li>
<li><a href="user-guide-basic-river-services.html">Getting started</a></li>
@@ -217,7 +239,7 @@ The preferred place of discussion on iss
<li><a href="resources.html">Resources</a></li>
<li><a href="building-a-release.html">Release</a></li>
</ul>
-<h3 id="community">Community</h3>
+<h3 id="community">Community<a class="headerlink" href="#community" title="Permanent link">¶</a></h3>
<ul>
<li><a href="get-involved.html">Get Involved</a></li>
<li>Discussion<ul>
@@ -233,7 +255,7 @@ The preferred place of discussion on iss
<li><a href="people.html">People</a></li>
<li><a href="found-a-bug.html">Found a Bug</a>?</li>
</ul>
-<h3 id="development">Development</h3>
+<h3 id="development">Development<a class="headerlink" href="#development" title="Permanent link">¶</a></h3>
<ul>
<li><a href="source-code.html">Source Code</a></li>
<li><a href="building-river.html">Building River</a></li>
@@ -243,7 +265,7 @@ The preferred place of discussion on iss
<li><a href="https://issues.apache.org/jira/browse/RIVER">Issue Tracker</a></li>
<li><a href="http://wiki.apache.org/river/">Wiki</a></li>
</ul>
-<h3 id="search">Search</h3>
+<h3 id="search">Search<a class="headerlink" href="#search" title="Permanent link">¶</a></h3>
<DIV>
<form method="get" action="http://www.google.com/search" id="search" name="search" style="font-size: 10px;">
<input type="hidden" name="sitesearch" value="river.apache.org">
Modified: websites/staging/river/trunk/content/discussion-futuredirection.html
==============================================================================
--- websites/staging/river/trunk/content/discussion-futuredirection.html (original)
+++ websites/staging/river/trunk/content/discussion-futuredirection.html Tue Sep 8 06:48:52 2015
@@ -66,7 +66,18 @@
<tr>
<td style="overflow: hidden;" valign="top" width="100%">
<div class="wiki-content">
-<h1 id="the-future-direction-of-river">The Future Direction of River</h1>
+<style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h1 id="the-future-direction-of-river">The Future Direction of River<a class="headerlink" href="#the-future-direction-of-river" title="Permanent link">¶</a></h1>
<p>There is currently a discussion on the dev mailing list which touches on the future of River. In particular if the focus of River should be geared towards direct support of "application" developers, support of developers writing "down stream" projects or both.</p>
<p>The discussion can be found in the <a href="http://mail-archives.apache.org/mod_mbox/river-dev/201012.mbox/%3cAANLkTi=+GrFS0-EJe+UBtkScU8JFYdpvo1EmoPOK2+6z@mail.gmail.com%3e">mail archive</a>.</p>
<p>This is currently unresolved.</p>
@@ -77,7 +88,18 @@
<div class="navigation_top">
<div class="navigation_bottom">
<!-- sidenav -->
-<h3 id="the-foundation">The Foundation</h3>
+<style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h3 id="the-foundation">The Foundation<a class="headerlink" href="#the-foundation" title="Permanent link">¶</a></h3>
<ul>
<li><a href="http://www.apache.org">Apache</a></li>
<li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
@@ -85,7 +107,7 @@
<li><a href="http://www.apache.org/security/">Security</a></li>
<li><a href="http://www.apache.org/foundation/how-it-works.html">How it works</a></li>
</ul>
-<h3 id="apache-river">Apache river</h3>
+<h3 id="apache-river">Apache river<a class="headerlink" href="#apache-river" title="Permanent link">¶</a></h3>
<ul>
<li><a href="downloads.html">Downloads</a></li>
<li><a href="maven-artifacts.html">Maven Artifacts</a></li>
@@ -93,7 +115,7 @@
<li><a href="index.html">News</a></li>
<li><a href="about.html">About</a></li>
</ul>
-<h3 id="documentation">Documentation</h3>
+<h3 id="documentation">Documentation<a class="headerlink" href="#documentation" title="Permanent link">¶</a></h3>
<ul>
<li><a href="concepts.html">Concepts</a></li>
<li><a href="user-guide-basic-river-services.html">Getting started</a></li>
@@ -105,7 +127,7 @@
<li><a href="resources.html">Resources</a></li>
<li><a href="building-a-release.html">Release</a></li>
</ul>
-<h3 id="community">Community</h3>
+<h3 id="community">Community<a class="headerlink" href="#community" title="Permanent link">¶</a></h3>
<ul>
<li><a href="get-involved.html">Get Involved</a></li>
<li>Discussion<ul>
@@ -121,7 +143,7 @@
<li><a href="people.html">People</a></li>
<li><a href="found-a-bug.html">Found a Bug</a>?</li>
</ul>
-<h3 id="development">Development</h3>
+<h3 id="development">Development<a class="headerlink" href="#development" title="Permanent link">¶</a></h3>
<ul>
<li><a href="source-code.html">Source Code</a></li>
<li><a href="building-river.html">Building River</a></li>
@@ -131,7 +153,7 @@
<li><a href="https://issues.apache.org/jira/browse/RIVER">Issue Tracker</a></li>
<li><a href="http://wiki.apache.org/river/">Wiki</a></li>
</ul>
-<h3 id="search">Search</h3>
+<h3 id="search">Search<a class="headerlink" href="#search" title="Permanent link">¶</a></h3>
<DIV>
<form method="get" action="http://www.google.com/search" id="search" name="search" style="font-size: 10px;">
<input type="hidden" name="sitesearch" value="river.apache.org">
Modified: websites/staging/river/trunk/content/discussion-internet.html
==============================================================================
--- websites/staging/river/trunk/content/discussion-internet.html (original)
+++ websites/staging/river/trunk/content/discussion-internet.html Tue Sep 8 06:48:52 2015
@@ -66,17 +66,28 @@
<tr>
<td style="overflow: hidden;" valign="top" width="100%">
<div class="wiki-content">
-<h1 id="river-on-the-internet-roti">River on the Internet (ROTI)</h1>
+<style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h1 id="river-on-the-internet-roti">River on the Internet (ROTI)<a class="headerlink" href="#river-on-the-internet-roti" title="Permanent link">¶</a></h1>
<p>Please participate on <a href="mailto:dev@river.apache.org">dev@river.apache.org</a></p>
-<h2 id="relevant-issues">Relevant issues</h2>
-<h3 id="trust">Trust</h3>
+<h2 id="relevant-issues">Relevant issues<a class="headerlink" href="#relevant-issues" title="Permanent link">¶</a></h2>
+<h3 id="trust">Trust<a class="headerlink" href="#trust" title="Permanent link">¶</a></h3>
<p>Centralized vs one to one trust relationships. Using TLS to establish trust.</p>
-<h3 id="code-deployment">Code deployment</h3>
+<h3 id="code-deployment">Code deployment<a class="headerlink" href="#code-deployment" title="Permanent link">¶</a></h3>
<p>Deploy code at runtime: only download from trusted source, not from anonymous http codebase server.</p>
<p>Deploy code at application deployment moment: included in application download (from appstore for instance)</p>
-<h3 id="nat-firewall-issues">NAT / Firewall issues</h3>
+<h3 id="nat-firewall-issues">NAT / Firewall issues<a class="headerlink" href="#nat-firewall-issues" title="Permanent link">¶</a></h3>
<p>Internet based proxies vs NAT traversal</p>
-<h3 id="discovery">Discovery</h3>
+<h3 id="discovery">Discovery<a class="headerlink" href="#discovery" title="Permanent link">¶</a></h3>
<p>Using existing reggie or new standard mechanisms like DNS-SD.</p>
</div>
</td>
@@ -85,7 +96,18 @@
<div class="navigation_top">
<div class="navigation_bottom">
<!-- sidenav -->
-<h3 id="the-foundation">The Foundation</h3>
+<style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h3 id="the-foundation">The Foundation<a class="headerlink" href="#the-foundation" title="Permanent link">¶</a></h3>
<ul>
<li><a href="http://www.apache.org">Apache</a></li>
<li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
@@ -93,7 +115,7 @@
<li><a href="http://www.apache.org/security/">Security</a></li>
<li><a href="http://www.apache.org/foundation/how-it-works.html">How it works</a></li>
</ul>
-<h3 id="apache-river">Apache river</h3>
+<h3 id="apache-river">Apache river<a class="headerlink" href="#apache-river" title="Permanent link">¶</a></h3>
<ul>
<li><a href="downloads.html">Downloads</a></li>
<li><a href="maven-artifacts.html">Maven Artifacts</a></li>
@@ -101,7 +123,7 @@
<li><a href="index.html">News</a></li>
<li><a href="about.html">About</a></li>
</ul>
-<h3 id="documentation">Documentation</h3>
+<h3 id="documentation">Documentation<a class="headerlink" href="#documentation" title="Permanent link">¶</a></h3>
<ul>
<li><a href="concepts.html">Concepts</a></li>
<li><a href="user-guide-basic-river-services.html">Getting started</a></li>
@@ -113,7 +135,7 @@
<li><a href="resources.html">Resources</a></li>
<li><a href="building-a-release.html">Release</a></li>
</ul>
-<h3 id="community">Community</h3>
+<h3 id="community">Community<a class="headerlink" href="#community" title="Permanent link">¶</a></h3>
<ul>
<li><a href="get-involved.html">Get Involved</a></li>
<li>Discussion<ul>
@@ -129,7 +151,7 @@
<li><a href="people.html">People</a></li>
<li><a href="found-a-bug.html">Found a Bug</a>?</li>
</ul>
-<h3 id="development">Development</h3>
+<h3 id="development">Development<a class="headerlink" href="#development" title="Permanent link">¶</a></h3>
<ul>
<li><a href="source-code.html">Source Code</a></li>
<li><a href="building-river.html">Building River</a></li>
@@ -139,7 +161,7 @@
<li><a href="https://issues.apache.org/jira/browse/RIVER">Issue Tracker</a></li>
<li><a href="http://wiki.apache.org/river/">Wiki</a></li>
</ul>
-<h3 id="search">Search</h3>
+<h3 id="search">Search<a class="headerlink" href="#search" title="Permanent link">¶</a></h3>
<DIV>
<form method="get" action="http://www.google.com/search" id="search" name="search" style="font-size: 10px;">
<input type="hidden" name="sitesearch" value="river.apache.org">
Modified: websites/staging/river/trunk/content/discussion-jarpackaging.html
==============================================================================
--- websites/staging/river/trunk/content/discussion-jarpackaging.html (original)
+++ websites/staging/river/trunk/content/discussion-jarpackaging.html Tue Sep 8 06:48:52 2015
@@ -66,11 +66,22 @@
<tr>
<td style="overflow: hidden;" valign="top" width="100%">
<div class="wiki-content">
-<h1 id="river-build-modularisation">River Build Modularisation</h1>
+<style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h1 id="river-build-modularisation">River Build Modularisation<a class="headerlink" href="#river-build-modularisation" title="Permanent link">¶</a></h1>
<p>There is a discussion on the mailing list about how best to package River, what 'modules' River is made out of and which classes belong in which JARs.</p>
<p>It's worth getting involved in this discussion since modifying the JAR structure may well have impact on users looking to migrate from the original Jini code or previous releases of River.</p>
<p>The discussion can be found in the <a href="http://mail-archives.apache.org/mod_mbox/river-dev/201101.mbox/%3c1293985847.3904.8.camel@cameron%3e">mail archive</a>.</p>
-<h1 id="modules">Modules</h1>
+<h1 id="modules">Modules<a class="headerlink" href="#modules" title="Permanent link">¶</a></h1>
<ul>
<li>Lookup "Reggie"</li>
<li>Transaction "Mahalo"</li>
@@ -93,7 +104,18 @@
<div class="navigation_top">
<div class="navigation_bottom">
<!-- sidenav -->
-<h3 id="the-foundation">The Foundation</h3>
+<style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h3 id="the-foundation">The Foundation<a class="headerlink" href="#the-foundation" title="Permanent link">¶</a></h3>
<ul>
<li><a href="http://www.apache.org">Apache</a></li>
<li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
@@ -101,7 +123,7 @@
<li><a href="http://www.apache.org/security/">Security</a></li>
<li><a href="http://www.apache.org/foundation/how-it-works.html">How it works</a></li>
</ul>
-<h3 id="apache-river">Apache river</h3>
+<h3 id="apache-river">Apache river<a class="headerlink" href="#apache-river" title="Permanent link">¶</a></h3>
<ul>
<li><a href="downloads.html">Downloads</a></li>
<li><a href="maven-artifacts.html">Maven Artifacts</a></li>
@@ -109,7 +131,7 @@
<li><a href="index.html">News</a></li>
<li><a href="about.html">About</a></li>
</ul>
-<h3 id="documentation">Documentation</h3>
+<h3 id="documentation">Documentation<a class="headerlink" href="#documentation" title="Permanent link">¶</a></h3>
<ul>
<li><a href="concepts.html">Concepts</a></li>
<li><a href="user-guide-basic-river-services.html">Getting started</a></li>
@@ -121,7 +143,7 @@
<li><a href="resources.html">Resources</a></li>
<li><a href="building-a-release.html">Release</a></li>
</ul>
-<h3 id="community">Community</h3>
+<h3 id="community">Community<a class="headerlink" href="#community" title="Permanent link">¶</a></h3>
<ul>
<li><a href="get-involved.html">Get Involved</a></li>
<li>Discussion<ul>
@@ -137,7 +159,7 @@
<li><a href="people.html">People</a></li>
<li><a href="found-a-bug.html">Found a Bug</a>?</li>
</ul>
-<h3 id="development">Development</h3>
+<h3 id="development">Development<a class="headerlink" href="#development" title="Permanent link">¶</a></h3>
<ul>
<li><a href="source-code.html">Source Code</a></li>
<li><a href="building-river.html">Building River</a></li>
@@ -147,7 +169,7 @@
<li><a href="https://issues.apache.org/jira/browse/RIVER">Issue Tracker</a></li>
<li><a href="http://wiki.apache.org/river/">Wiki</a></li>
</ul>
-<h3 id="search">Search</h3>
+<h3 id="search">Search<a class="headerlink" href="#search" title="Permanent link">¶</a></h3>
<DIV>
<form method="get" action="http://www.google.com/search" id="search" name="search" style="font-size: 10px;">
<input type="hidden" name="sitesearch" value="river.apache.org">
Modified: websites/staging/river/trunk/content/documentation.html
==============================================================================
--- websites/staging/river/trunk/content/documentation.html (original)
+++ websites/staging/river/trunk/content/documentation.html Tue Sep 8 06:48:52 2015
@@ -66,9 +66,20 @@
<tr>
<td style="overflow: hidden;" valign="top" width="100%">
<div class="wiki-content">
-<h1 id="apache-river-documentation">Apache River Documentation</h1>
+<style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h1 id="apache-river-documentation">Apache River Documentation<a class="headerlink" href="#apache-river-documentation" title="Permanent link">¶</a></h1>
<p>The original Jini documentation (including the formal specifications) can be found <a href="http://river.apache.org/doc/index.html">here</a>. For more general help and information please see the list of topics below.</p>
-<table>
+<table class="table">
<thead>
<tr>
<th>Document</th>
@@ -97,7 +108,18 @@
<div class="navigation_top">
<div class="navigation_bottom">
<!-- sidenav -->
-<h3 id="the-foundation">The Foundation</h3>
+<style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h3 id="the-foundation">The Foundation<a class="headerlink" href="#the-foundation" title="Permanent link">¶</a></h3>
<ul>
<li><a href="http://www.apache.org">Apache</a></li>
<li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
@@ -105,7 +127,7 @@
<li><a href="http://www.apache.org/security/">Security</a></li>
<li><a href="http://www.apache.org/foundation/how-it-works.html">How it works</a></li>
</ul>
-<h3 id="apache-river">Apache river</h3>
+<h3 id="apache-river">Apache river<a class="headerlink" href="#apache-river" title="Permanent link">¶</a></h3>
<ul>
<li><a href="downloads.html">Downloads</a></li>
<li><a href="maven-artifacts.html">Maven Artifacts</a></li>
@@ -113,7 +135,7 @@
<li><a href="index.html">News</a></li>
<li><a href="about.html">About</a></li>
</ul>
-<h3 id="documentation">Documentation</h3>
+<h3 id="documentation">Documentation<a class="headerlink" href="#documentation" title="Permanent link">¶</a></h3>
<ul>
<li><a href="concepts.html">Concepts</a></li>
<li><a href="user-guide-basic-river-services.html">Getting started</a></li>
@@ -125,7 +147,7 @@
<li><a href="resources.html">Resources</a></li>
<li><a href="building-a-release.html">Release</a></li>
</ul>
-<h3 id="community">Community</h3>
+<h3 id="community">Community<a class="headerlink" href="#community" title="Permanent link">¶</a></h3>
<ul>
<li><a href="get-involved.html">Get Involved</a></li>
<li>Discussion<ul>
@@ -141,7 +163,7 @@
<li><a href="people.html">People</a></li>
<li><a href="found-a-bug.html">Found a Bug</a>?</li>
</ul>
-<h3 id="development">Development</h3>
+<h3 id="development">Development<a class="headerlink" href="#development" title="Permanent link">¶</a></h3>
<ul>
<li><a href="source-code.html">Source Code</a></li>
<li><a href="building-river.html">Building River</a></li>
@@ -151,7 +173,7 @@
<li><a href="https://issues.apache.org/jira/browse/RIVER">Issue Tracker</a></li>
<li><a href="http://wiki.apache.org/river/">Wiki</a></li>
</ul>
-<h3 id="search">Search</h3>
+<h3 id="search">Search<a class="headerlink" href="#search" title="Permanent link">¶</a></h3>
<DIV>
<form method="get" action="http://www.google.com/search" id="search" name="search" style="font-size: 10px;">
<input type="hidden" name="sitesearch" value="river.apache.org">