You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@river.apache.org by wa...@apache.org on 2021/06/01 23:30:03 UTC
[river-site] 03/06: fix issues mixing html and markdown. Add title
to index.md
This is an automated email from the ASF dual-hosted git repository.
wave pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/river-site.git
commit ce21758e32d04ac54acec38af130900434160447
Author: Dave Fisher <da...@davefisher.tech>
AuthorDate: Tue Jun 1 15:53:16 2021 -0700
fix issues mixing html and markdown. Add title to index.md
---
content/dev-doc/building-a-release.md | 17 +++++++++++++++--
content/dev-doc/building-river.md | 19 ++++++++++++++++++
content/dev-doc/ci.md | 5 ++++-
content/dev-doc/development-process.md | 12 ++++++++++++
content/dev-doc/source-code.md | 5 -----
content/discussion-futuredirection.md | 2 +-
content/index.md | 1 +
content/license-notice.md | 2 --
content/user-doc/get-involved.md | 5 ++---
content/user-doc/getting-started.md | 34 ++++++++++++++++-----------------
content/user-doc/helloworld.md | 2 +-
content/user-doc/mailing-lists.md | 1 +
content/user-doc/releases.md | 9 +++++++++
content/user-doc/success-stories.md | 10 ++++++++++
content/user-doc/supported-platforms.md | 10 +++-------
15 files changed, 94 insertions(+), 40 deletions(-)
diff --git a/content/dev-doc/building-a-release.md b/content/dev-doc/building-a-release.md
index 4f520ed..97cf868 100644
--- a/content/dev-doc/building-a-release.md
+++ b/content/dev-doc/building-a-release.md
@@ -8,22 +8,25 @@ license: https://www.apache.org/licenses/LICENSE-2.0
<div class="space-mn"></div>
+
### KEYS file
Add your key to the KEYS file in the repo
<div class="space-mn"></div>
+
### Checkout The Source
svn checkout https://svn.apache.org/repos/asf/river/jtsk/trunk river
<div class="space-mn"></div>
+
### Pre release checks
- * River-trunk should run successful.
- * River-verify should run successful. (not yet?)
+* River-trunk should run successful.
+* River-verify should run successful. (not yet?)
<div class="space-mn"></div>
@@ -41,6 +44,7 @@ The release notes need to be pasted into;
<div class="space-mn"></div>
+
### Update Version Numbers
There are version numbers in the following places that need to be updated with the new release number/name.
@@ -52,30 +56,35 @@ In the above HTML page, there is also a section on "changes by component" which
<div class="space-mn"></div>
+
### Branch the repository
svn cp https://svn.apache.org/repos/asf/river/jtsk/trunk https://svn.apache.org/repos/asf/river/jtsk/branches/$VERSION
<div class="space-mn"></div>
+
### Tag the repository
svn cp https://svn.apache.org/repos/asf/river/jtsk/trunk https://svn.apache.org/repos/asf/river/jtsk/tags/$VERSION
<div class="space-mn"></div>
+
### Build the release products
ant -Dversion=$VERSION clean release
<div class="space-mn"></div>
+
### Rat Reports
./rat_reports.sh
<div class="space-mn"></div>
+
### Sign the release
- [General Apache Signing Details][1]
@@ -90,6 +99,7 @@ In the above HTML page, there is also a section on "changes by component" which
<div class="space-mn"></div>
+
### Test the release
cp dist/apache-river-$VERSION.tar.gz $SOMEWHERE_ELSE
@@ -100,6 +110,7 @@ In the above HTML page, there is also a section on "changes by component" which
<div class="space-mn"></div>
+
### Upload the release
scp RAT* username@people.apache.org:~/public_html/river/
@@ -108,6 +119,7 @@ In the above HTML page, there is also a section on "changes by component" which
<div class="space-mn"></div>
+
### Allow the community to evaluate the release products
* announce availability of candidate on river-dev.
@@ -115,6 +127,7 @@ In the above HTML page, there is also a section on "changes by component" which
<div class="space-mn"></div>
+
### Publish release on website
* checkout the site
* Extract the javadocs from the release archive into ...
diff --git a/content/dev-doc/building-river.md b/content/dev-doc/building-river.md
index 87ec466..c1c6968 100644
--- a/content/dev-doc/building-river.md
+++ b/content/dev-doc/building-river.md
@@ -5,6 +5,7 @@ license: https://www.apache.org/licenses/LICENSE-2.0
## Building River
<div class="space-sm"></div>
+
### Prerequisites
In order to build River, you need the following tools:
@@ -16,6 +17,7 @@ The rest is included in the source archive, and in the SVN.
This article also describes how to setup your IDE to compile River.
<div class="space-mn"></div>
+
### Spaces in paths
<span class="label label-warning">Warning</span>
@@ -33,11 +35,13 @@ If you are running on Windows, it is also advisable to use a forward slash '/' a
<div class="space-mn"></div>
+
### Check out the code
See [this page](source-code.html) on how to check out the source code.
<div class="space-mn"></div>
+
### Build the distribution
River can be built simply by running Ant from where you checked the code out from.
@@ -50,8 +54,11 @@ Assume "$RIVER_HOME" is where you have checked out the code to.
Will build all the River JARs required. You will then find them in the $ {RIVER_HOME}/lib* directories.
<div class="space-mn"></div>
+
### Setting up the IDE
+
<div class="space-mn"></div>
+
#### Eclipse
Create your new IDE project using your prefered method (e.g. "Import from SVN" or create a new project using existing source, etc).
@@ -64,7 +71,9 @@ Currently, River should be built with JDK 6 (-source 5), so please ensure that y
Then you need to add the JARs in `$RIVER_HOME/extlibs` to your classpath.
That should everything that Eclipse needs to be happy with the River code.
+
<div class="space-mn"></div>
+
#### NetBeans
* Checkout the trunk.
* In Netbeans 7.2 do:
@@ -75,11 +84,13 @@ That should everything that Eclipse needs to be happy with the River code.
<div class="space-lg"></div>
+
## Testing River
This build process runs the (limited) suite of unit tests that comes with River. River is tested predominantly by using [jtreg](http://openjdk.java.net/jtreg/) and the QA test suite.
<div class="space-mn"></div>
+
### The JUnit tests
The JUnit tests can be found in `$RIVER_HOME/test/src` you must also add the JARs found in `$RIVER_HOME/test/lib` onto the classpath for your tests.
@@ -87,6 +98,7 @@ The JUnit tests can be found in `$RIVER_HOME/test/src` you must also add the JAR
It's easiest to run these tests from your IDE. In Eclipse, for example, once `$RIVER_HOME/test/src` is set at the test source directory, right-clicking the project and hitting "Run as JUnit test" is all that is required.
<div class="space-mn"></div>
+
### The QA Test Suite
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.
@@ -107,10 +119,12 @@ Execute the following:
cd qa.run
<div class="space-mn"></div>
+
#### Running just a few tests
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.
<div class="space-mn"></div>
+
##### By settings in the properties file
When running the QA tests with Ant, this is done by including the following in the Ant build.properties file.
@@ -123,6 +137,7 @@ When running the QA tests with Ant, this is done by including the following in t
run.tests=path/to/test/TestName.td
<div class="space-mn"></div>
+
##### By specifying on the commandline
From the qa directory:
@@ -131,10 +146,12 @@ From the qa directory:
Existing QA tests can be found in the following path; `$RIVER_HOME/qa/src/com/sun/jini/test/**"`
<div class="space-mn"></div>
+
#### Categories
You can find the test categories on [Test categories](testing-categories.html)
<div class="space-mn"></div>
+
### JTREG tests
You must first download and install jtreg following the instructions on their site.
@@ -156,11 +173,13 @@ The JTREG tests can then be run by execute the following:
JTREG will create the directory `$RIVER_HOME/qa/jtreg/JTreport` which contains a report of the test run.
<div class="space-mn"></div>
+
#### Running specific JTREG tests
_todo_
<div class="space-mn"></div>
+
#### Known Problems
There are the following known problems with the jtreg tests:
diff --git a/content/dev-doc/ci.md b/content/dev-doc/ci.md
index 61f0754..27a4462 100644
--- a/content/dev-doc/ci.md
+++ b/content/dev-doc/ci.md
@@ -11,7 +11,7 @@ After changes the builds are scheduled on the [Apache build server](https://buil
The following jobs are used:
Job | Role
-- | -
+--|--
River-trunk-* | Builds the trunk, and check for compilation errors only
River-QA-* | Builds the trunk and run QA tests
River-verify |
@@ -21,12 +21,14 @@ River-QA-Runtime |
For their current status, see: <https://builds.apache.org/view/M-R/view/River/>
<div class="space-mn"></div>
+
### River-trunk jobs
The River trunk build is only run on Ubuntu. The naming scheme is:
River-trunk-[jdkid]
<div class="space-mn"></div>
+
### River-QA- jobs
The River QA jobs naming scheme used is: River-QA-[platformid]-[jdkid] optional [-branchid]
@@ -35,6 +37,7 @@ and tests the river-runtime with the river-qa framework.
<div class="space-mn"></div>
+
### Platforms and Jdks
The current platforms are: Solaris, Ubuntu, Windows
diff --git a/content/dev-doc/development-process.md b/content/dev-doc/development-process.md
index 8cf9703..434041d 100644
--- a/content/dev-doc/development-process.md
+++ b/content/dev-doc/development-process.md
@@ -5,6 +5,7 @@ license: https://www.apache.org/licenses/LICENSE-2.0
[TOC]
### River Development Process
+
<div class="space-lg"></div>
#### River build server
@@ -12,6 +13,7 @@ license: https://www.apache.org/licenses/LICENSE-2.0
River is built on the Apache Hudson server. The projects can be found [here](https://hudson.apache.org/hudson/view/M-R/view/River/). More on this process: [Continuous Integration](ci.html)
<div class="space-mn"></div>
+
#### Tracking issues and changes
* A JIRA issue is required for any substantive change.
@@ -24,6 +26,7 @@ The preferred place of discussion on issues is the river-dev mail list. A link t
<div class="space-mn"></div>
+
#### Handling Security -related Issues
There are three options associated with the "Security Level" field in the JIRA instance:
@@ -38,6 +41,7 @@ If the issue is acknowledged as a valid security issue, a JIRA issue needs to be
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.
<div class="space-mn"></div>
+
#### Code Reviews
* for public API changes:
@@ -48,6 +52,7 @@ As soon as appropriate (for example, when the impact is understood and/or there
<div class="space-mn"></div>
+
#### Testing
Developing test cases and running test suites are desired but not required prior to an integration. If unit tests are
@@ -198,6 +203,7 @@ Here is a list of individually executable
<div class="space-mn"></div>
+
#### Version Numbering
Each Apache River deliverable has a version number of:
@@ -212,6 +218,7 @@ The major version number will in general only be increased in case of major chan
<div class="space-mn"></div>
+
#### Branching Policy
Ongoing development for the next release takes place in the `/trunk`. Once feature complete for a (non maintenance) release the trunk is branched into `/branches/<m.n>` 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 `/trunk`, issues found against the release candidate will be fixed in `/branches/<m.n>` and likely merged into the `/trunk`.
@@ -256,18 +263,22 @@ Although ongoing development should take place in `/trunk`, there is a `/skunk`
<div class="space-sm"></div>
+
### Coding conventions
<div class="space-mn"></div>
+
#### Indentation
Tabs are not used. Default indentation is 4 spaces.
<div class="space-mn"></div>
+
#### Other
Contributors are advised to read the [Code Conventions for the Java](http://www.oracle.com/technetwork/java/codeconvtoc-136057.html)
and try to adhere as much as possible to these conventions.
<div class="space-mn"></div>
+
#### Reformatting
If the reformatting involves a large part of the code,
a clearly labeled 'reformatting' commit in between is recommended.
@@ -275,6 +286,7 @@ Keeping your reformatting changes limited,
reduces the change of merging conflicts by your fellow committers.
<div class="space-mn"></div>
+
#### Older sources
We do not actively search and reformat source files
that are not formatted according to this convention.
diff --git a/content/dev-doc/source-code.md b/content/dev-doc/source-code.md
index 908753c..000deea 100644
--- a/content/dev-doc/source-code.md
+++ b/content/dev-doc/source-code.md
@@ -9,7 +9,6 @@ River uses [Subversion](http://subversion.tigris.org/) to manage its source code
The source code for the various deliverables of Apache River can be freely browsed at <http://svn.apache.org/viewvc/river/>.
-####
#### Anonymous access
@@ -23,7 +22,6 @@ release was in the 2.2 branch.
svn checkout http://svn.apache.org/repos/asf/river/jtsk/branches/2.2
-####
#### Access from behind a firewall
@@ -33,7 +31,6 @@ you can try to access it via HTTPS:
svn checkout https://svn.apache.org/repos/asf/river/jtsk/trunk river
-####
#### Access through a proxy
@@ -53,7 +50,6 @@ Example : Edit the 'servers' file and add something like :
http-proxy-port = 3128
-####
#### Submitting a Patch
If you make changes to River, and would like to contribute the to the project, you should create a patch and post it
@@ -66,7 +62,6 @@ following command:
If you've added new files, remember to "svn add" them so they get included in the diff.
-####
#### Developer Access
Everyone can access the River Subversion repository via HTTPS, but River Committers must checkout the Subversion
diff --git a/content/discussion-futuredirection.md b/content/discussion-futuredirection.md
index 803abdb..f3cfeb4 100644
--- a/content/discussion-futuredirection.md
+++ b/content/discussion-futuredirection.md
@@ -1,7 +1,7 @@
Title: Future direction
license: https://www.apache.org/licenses/LICENSE-2.0
-#The Future Direction of River
+# The Future Direction of River
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.
diff --git a/content/index.md b/content/index.md
index ccecdd4..8c81e4e 100644
--- a/content/index.md
+++ b/content/index.md
@@ -1,3 +1,4 @@
+title: Home Page
license: https://www.apache.org/licenses/LICENSE-2.0
diff --git a/content/license-notice.md b/content/license-notice.md
deleted file mode 100644
index b6d01b4..0000000
--- a/content/license-notice.md
+++ /dev/null
@@ -1,2 +0,0 @@
-license: https://www.apache.org/licenses/LICENSE-2.0
-
diff --git a/content/user-doc/get-involved.md b/content/user-doc/get-involved.md
index 6292e46..e805fd2 100644
--- a/content/user-doc/get-involved.md
+++ b/content/user-doc/get-involved.md
@@ -6,6 +6,7 @@ license: https://www.apache.org/licenses/LICENSE-2.0
The Apache River project is being built by the open source community for the open source community. We truly welcome your input and contributions!
<div class="space-mn"></div>
+
### What we are looking for:
@@ -21,7 +22,6 @@ The Apache River project is being built by the open source community for the ope
<div class="alert alert-info" style="font-size: 17px; margin: 5% 10%">
A recent <a href="http://mail-archives.apache.org/mod_mbox/river-dev/201802.mbox/%3cCAEdUjjj+OCs_Q5sLaSQmBEJsKKF-En0432YWoTcN4PzppmTMiw@mail.gmail.com%3e">initiative</a>
aims at revising JINI specifications:
-
<blockquote class="blockquote">
<small>
"The idea is to prioritize the modernization of the River
@@ -34,15 +34,14 @@ The Apache River project is being built by the open source community for the ope
<p>
<a href="#" class="alert-link">Help the community in this exciting modernization plan!</a>
</p>
-
Read the above thread to get a context, use <a href="https://issues.apache.org/jira/browse/RIVER-450">JIRA</a> to find a
task you are interested in and follow our <a href="https://river.apache.org/dev-doc/source-code.html">source code guidelines</a>
to submit changes to specifications.
-
Thank you!
</div>
<div class="space-mn"></div>
+
### How do I contribute?
* To discuss Apache River topics check out the [mailing lists](mailing-lists.html).
diff --git a/content/user-doc/getting-started.md b/content/user-doc/getting-started.md
index 426a22c..ce9b0f1 100644
--- a/content/user-doc/getting-started.md
+++ b/content/user-doc/getting-started.md
@@ -17,7 +17,6 @@ from what you'll see below, so you can progress with the binary release if you w
If you are going to use the latest release then you will still need to download (from the SVN trunk) some of the
Windows BAT files mentioned below. *nix sh scripts of those same batch files will appear shortly.
-####
<div class="panel panel-default">
<div class="panel-heading">Environment Setup</div>
<div class="panel-body">
@@ -26,14 +25,14 @@ The following instructions all assume that you have checked out River to some di
to as `$RIVER_HOME`. Further, you have changed directory into `$RIVER_HOME/examples/hello`.
<div class="alert alert-info">
- Run all scripts from the `hello` directory
-</div>
+Run all scripts from the `hello` directory
+
+</div>
- Change directory to $RIVER_HOME
- Use Ant to build River, i.e. `ant all.build`
-####
#### Running Code Which Uses River Services
Since River uses dynamic code downloading, we need to grant various permissions to our JVM to allow that. In the
@@ -59,12 +58,9 @@ Also, before doing anything with any River code you need to set an appropriate s
done only once per program.
System.setSecurityManager(new RMISecurityManager());
+
</div>
</div>
-
-
-
-####
<div class="panel panel-default">
<div class="panel-heading">Starting the HTTP server</div>
<div class="panel-body">
@@ -80,8 +76,10 @@ See [3.2 How codebase is used in Java RMI](http://download.oracle.com/javase/1.5
more details.
<div class="alert alert-info">
+
- Change to directory to `$RIVER_HOME/examples/hello/` <br/>
- Execute the script; `scripts/httpd.bat` <br/>
+
</div>
#### Testing it
@@ -89,12 +87,9 @@ more details.
To test that the HTTP server is running correctly use wget or your web browser on the following URL
- http://localhost:8080/reggie-dl.jar
+
</div>
</div>
-
-
-
-####
<div class="panel panel-default">
<div class="panel-heading">Starting a Service Registrar (Lookup Service)</div>
<div class="panel-body">
@@ -108,8 +103,10 @@ federated space.
Broadly speaking (although not 100% accurately) you need a Lookup Service in order to be able to find other services to use.
<div class="alert alert-info">
+
- Change to directory to `$RIVER_HOME/examples/hello/` <br/>
- Execute the script; `scripts/jrmp-reggie.bat` <br/>
+
</div>
@@ -162,11 +159,9 @@ not your Lookup Service is running.
This approach can be modified if you know which hosts on the subnet _might_ be running lookup services. You can
define and pass this list to the `LookupDiscovery` constructor.
+
</div>
</div>
-
-
-####
<div class="panel panel-default">
<div class="panel-heading">Starting a Java Space</div>
<div class="panel-body">
@@ -178,8 +173,10 @@ now we're going to start a Java Space, and find that. Using the Java Space is o
although the "how" is relatively straightforward.
<div class="alert alert-info">
+
- Change to directory to `$RIVER_HOME/examples/hello/` <br/>
- Execute the script; `scripts/jrmp-outrigger-group` <br/>
+
</div>
##### Testing it
@@ -214,11 +211,9 @@ Using the `ServiceDiscoveryManager` is similar;
else {
System.out.println("No Java Space found.");
}
+
</div>
</div>
-
-
-####
<div class="panel panel-default">
<div class="panel-heading">Starting a Transaction Service</div>
<div class="panel-body">
@@ -228,8 +223,10 @@ Using the `ServiceDiscoveryManager` is similar;
Because you'd like to find something that will give you a nice distributed transaction.
<div class="alert alert-info">
+
- Change to directory to `$RIVER_HOME/examples/hello/` <br/>
- Execute the script; `scripts/jrmp-mahalo-group` <br/>
+
</div>
##### Testing it
@@ -237,5 +234,6 @@ Because you'd like to find something that will give you a nice distributed trans
Testing it is done in the same way as for the Java Space. However, the constructor of the `ServiceTemplate` changes.
ServiceTemplate template = new ServiceTemplate(null, new Class[) { TransactionManager.class }, new Entry[0](0.html));
+
</div>
</div>
diff --git a/content/user-doc/helloworld.md b/content/user-doc/helloworld.md
index 8694cfb..21f51a7 100644
--- a/content/user-doc/helloworld.md
+++ b/content/user-doc/helloworld.md
@@ -1,4 +1,4 @@
-Title:
+Title: Hello World
license: https://www.apache.org/licenses/LICENSE-2.0
# Hello World With River
diff --git a/content/user-doc/mailing-lists.md b/content/user-doc/mailing-lists.md
index 40bbbba..55780fd 100644
--- a/content/user-doc/mailing-lists.md
+++ b/content/user-doc/mailing-lists.md
@@ -5,6 +5,7 @@ license: https://www.apache.org/licenses/LICENSE-2.0
### Mailing Lists
<div class="space-mn"></div>
+
#### user@river.apache.org
This list is for people using Apache ACE. Please note that during incubation, we only had a developer list, which means
diff --git a/content/user-doc/releases.md b/content/user-doc/releases.md
index 27dfba2..1acf94a 100644
--- a/content/user-doc/releases.md
+++ b/content/user-doc/releases.md
@@ -10,6 +10,7 @@ Apache River releases are available under the [Apache License, Version 2.0](http
<div class="space-mn"></div>
+
### Apache River v3.0.0 (Released October 5, 2016)
This is the "Jini Technology Starter Kit", or "JTSK", i.e. the complete source for River and the infrastructure services.
@@ -24,6 +25,7 @@ _Note:_ No jar files published in Maven Central at present.
<div class="space-mn"></div>
+
### Apache River Examples v1.0 (Released Aug 10, 2015)
The examples project contains a set of introductory examples of River services and clients. This project builds
@@ -39,9 +41,11 @@ Unpack the examples project and follow the instructions in 'README.md' at the to
<div class="space-lg"></div>
+
## Archived Releases
<div class="space-mn"></div>
+
### Apache River v2.2.3 (Released Feb 21, 2016)
_Note:_ To experiment with River, you generally don't need to build from source. You're probably better off starting with the the
@@ -53,6 +57,7 @@ examples project, which will automatically get the prebuilt jar files from Maven
* [apache-river-2.2.3-doc.tar.gz](http://www.apache.org/dyn/closer.cgi/river/river-2.2.3/apache-river-2.2.3-bin.tar.gz) ([PGP](http://www.apache.org/dist/river/river-2.2.3/apache-river-2.2.3-doc.tar.gz.asc), [SHA1](http://www.apache.org/dist/river/river-2.2.3/apache-river-2.2.3-doc.tar.gz.sha))
<div class="space-mn"></div>
+
### Apache River v2.2.2 (Released Nov. 18, 2013)
* [apache-river-2.2.2-src.zip](http://archive.apache.org/dist/river/river-2.2.2/apache-river-2.2.2-src.zip) ([PGP](http://www.apache.org/dist/river/river-2.2.2/apache-river-2.2.2-src.zip.asc), [SHA1](http://www.apache.org/dist/river/river-2.2.2/apache-river-2.2.2-src.zip.sha))
@@ -62,6 +67,7 @@ examples project, which will automatically get the prebuilt jar files from Maven
<div class="space-mn"></div>
+
### Apache River v2.2.1 (Released May 4, 2013)
* [apache-river-2.2.1-src.zip](http://archive.apache.org/dist/river/river-2.2.1/apache-river-2.2.1-src.zip) ([PGP](http://www.apache.org/dist/river/river-2.2.1/apache-river-2.2.1-src.zip.asc), [SHA1](http://www.apache.org/dist/river/river-2.2.1/apache-river-2.2.1-src.zip.sha))
@@ -71,6 +77,7 @@ examples project, which will automatically get the prebuilt jar files from Maven
<div class="space-mn"></div>
+
### Apache River v2.2.0 (First Top Level Project release)
* [apache-river-2.2.0-src.zip](http://archive.apache.org/dist/river/river-2.2.0/apache-river-2.2.0-src.zip) ([PGP](http://www.apache.org/dist/river/river-2.2.0/apache-river-2.2.0-src.zip.asc), [SHA1](http://www.apache.org/dist/river/river-2.2.0/apache-river-2.2.0-src.zip.sha))
@@ -80,6 +87,7 @@ examples project, which will automatically get the prebuilt jar files from Maven
<div class="space-lg"></div>
+
## Continuous snapshots
Download the build artifacts from our [trunk build](https://builds.apache.org/pview/job/River-trunk-jdk7/lastSuccessfulBuild)
@@ -98,6 +106,7 @@ and the 2.1.x releases made during incubation are available from the [Incubator
<div class="space-lg"></div>
+
## PGP Signatures
All of the release distribution packages have been digitally signed (using PGP or GPG) by the Apache Group members that constructed them. There will be an accompanying distribution.asc file in the same directory as the distribution. The PGP keys can be found in the MIT key repository (hkp://pgp.mit.edu), the OpenPGP Public Key repository (hkp://subkeys.pgp.net), and within this project's KEYS file, which is located within each download directory.
diff --git a/content/user-doc/success-stories.md b/content/user-doc/success-stories.md
index 3a6d5fe..cd52dfb 100644
--- a/content/user-doc/success-stories.md
+++ b/content/user-doc/success-stories.md
@@ -5,7 +5,9 @@ license: https://www.apache.org/licenses/LICENSE-2.0
### Success Stories
<div class="space-mn"></div>
+
#### [](https://travellinck.com)
+
<blockquote>
<small>
<p>
@@ -49,18 +51,22 @@ Dawid Loubser
</blockquote>
<div class="space-mn"></div>
+
#### [](https://www.blazegraph.com)
Blazegraph™ is a ultra high-performance graph database supporting Apache TinkerPop™ and RDF/SPARQL APIs.
It supports up to 50 Billion edges on a single machine.
<div class="space-mn"></div>
+
#### [](https://www.gigaspaces.com)
GigaSpaces provides the leading in-memory computing platform for fast data analytics and extreme transaction processing.
<div class="space-mn"></div>
+
#### [](http://www.sucdenfinancial.com)
+
<blockquote>
<small>
<p>
@@ -114,6 +120,7 @@ Front Office Development Manager, Sucden Financial Limited.
</blockquote>
<div class="space-mn"></div>
+
#### Blitz
A performant, persistent implementation of the JavaSpaces API, which is much more suitable for enterprise-grade use
than the (in-memory only) reference implementation, Outrigger [see here](https://github.com/dancres/blitzjavaspaces).
@@ -129,6 +136,7 @@ A re-packaging of the Blitz project to build with Maven is available [here](http
-->
<div class="space-mn"></div>
+
#### Rio
[Rio](http://www.rio-project.org) is an open source technology that provides a dynamic architecture for developing, deploying and managing distributed systems composed of services.
@@ -149,6 +157,7 @@ Key features include:
1. Maven based artifact resolution
<div class="space-mn"></div>
+
#### JGDMS - Java Global Discovered Micro Services
The [github code](https://pfirmstone.github.io/JGDMS/) is forked off River trunk, just before the Ivy dependency build
changes and the 3.0 release was branched.
@@ -168,6 +177,7 @@ Additions include:
As soon as River community decides these improvements can be integrated back.
<div class="space-sm"></div>
+
#### Jini Success Stories
- [Original Jini.org success stories](http://www.jini.org/wiki/Who_uses_Jini%3F), including:
1. [TNO ICT, The Netherlands](http://www.tno.nl/informatie-_en_communicatietechnologie/)
diff --git a/content/user-doc/supported-platforms.md b/content/user-doc/supported-platforms.md
index a25e7f8..86220f1 100644
--- a/content/user-doc/supported-platforms.md
+++ b/content/user-doc/supported-platforms.md
@@ -4,23 +4,19 @@ license: https://www.apache.org/licenses/LICENSE-2.0
### Supported platforms
-####
-
#### Operating systems
OS | Remarks
--- | ----
+---|-----
solaris |
ubuntu |
windows |
freebsd | No recent information available: No up to date JDK available.
osx | No recent information available: [osx build server unavailable](http://mail-archives.apache.org/mod_mbox/www-builds/201111.mbox/%3CCAOJNCYcgMtCrHeE4+MbOcnBRPELaVryoR7+4YpzFr3kwkto0TQ@mail.gmail.com%3E)
-####
-
#### Java runtime versions
Version | Remarks
-------- | -----
+--------|------
7 |
6 |
1.5 | river-qa does not compile
@@ -39,7 +35,7 @@ The com.sun.* packages are only available on Sun/Oracle based JDK's
#### Authentication subsystems
System | Remarks
------- | -------
+-------|-------
Kerberos | Untested
#### Testing framework