Author: sijskes
Date: Wed Aug 8 10:00:24 2012
New Revision: 1370723
URL: http://svn.apache.org/viewvc?rev=1370723&view=rev
Log:
Applied RIVER-408 patch. thanks to Damjan Jovanovic
Modified:
river/site/trunk/content/discussion-futuredirection.mdtext
river/site/trunk/content/discussion-jarpackaging.mdtext
river/site/trunk/content/index.mdtext
river/site/trunk/content/user-guide-river-jar-artifacts.mdtext
Modified: river/site/trunk/content/discussion-futuredirection.mdtext
URL:
http://svn.apache.org/viewvc/river/site/trunk/content/discussion-futuredirection.mdtext?rev=1370723&r1=1370722&r2=1370723&view=diff
==============================================================================
--- river/site/trunk/content/discussion-futuredirection.mdtext (original)
+++ river/site/trunk/content/discussion-futuredirection.mdtext Wed Aug 8
10:00:24 2012
@@ -20,6 +20,6 @@ Notice: Licensed to the Apache Softwa
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.
-The discussion can be found in the [mail
archive](http://mail-archives.apache.org/mod_mbox/incubator-river-dev/201012.mbox/%[email protected]%3e).
+The discussion can be found in the [mail
archive](http://mail-archives.apache.org/mod_mbox/river-dev/201012.mbox/%[email protected]%3e).
-This is currently unresolved.
\ No newline at end of file
+This is currently unresolved.
Modified: river/site/trunk/content/discussion-jarpackaging.mdtext
URL:
http://svn.apache.org/viewvc/river/site/trunk/content/discussion-jarpackaging.mdtext?rev=1370723&r1=1370722&r2=1370723&view=diff
==============================================================================
--- river/site/trunk/content/discussion-jarpackaging.mdtext (original)
+++ river/site/trunk/content/discussion-jarpackaging.mdtext Wed Aug 8 10:00:24
2012
@@ -22,7 +22,7 @@ There is a discussion on the mailing lis
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.
-The discussion can be found in the [mail
archive](http://mail-archives.apache.org/mod_mbox/incubator-river-dev/201101.mbox/%3c1293985847.3904.8.camel@cameron%3e).
+The discussion can be found in the [mail
archive](http://mail-archives.apache.org/mod_mbox/river-dev/201101.mbox/%3c1293985847.3904.8.camel@cameron%3e).
# Modules
@@ -37,4 +37,4 @@ The discussion can be found in the [mail
* iiop
* jeri
* jrmp
-
\ No newline at end of file
+
Modified: river/site/trunk/content/index.mdtext
URL:
http://svn.apache.org/viewvc/river/site/trunk/content/index.mdtext?rev=1370723&r1=1370722&r2=1370723&view=diff
==============================================================================
--- river/site/trunk/content/index.mdtext (original)
+++ river/site/trunk/content/index.mdtext Wed Aug 8 10:00:24 2012
@@ -19,7 +19,7 @@ Follow and participate in the vibrant de
the challenges of fixing bugs in a multi version compatibility environment,
the adoption of generics, by subscribing to
[river-dev](mailto:[email protected]).
-To see the full discussion, go to the archive:
[mail-archives.apache.org](http://mail-archives.apache.org/mod_mbox/incubator-river-dev/)
+To see the full discussion, go to the archive:
[mail-archives.apache.org](http://mail-archives.apache.org/mod_mbox/river-dev/)
# Apache River graduation
After years of hard work, the contributions of many finally pay off.
@@ -39,7 +39,7 @@ Feel free to join in and assist by insta
The first project release (v2.1.1 incubating) from the River project has been
approved by the River Community.
-[Here](http://mail-archives.apache.org/mod_mbox/incubator-river-dev/200801.mbox/%[email protected]%3E)
are the Vote Results
+[Here](http://mail-archives.apache.org/mod_mbox/river-dev/200801.mbox/%[email protected]%3E)
are the Vote Results
Next step is to get Apache Incubator approval for the release.
@@ -80,4 +80,4 @@ River is actively looking for people who
* River-342: [Jini in a Jar - some helpful utilities for
newbie's](https://issues.apache.org/jira/browse/RIVER-342)
* River-337: [Attempted discard of unknown registrar kills
LookupLocatorDiscovery thread](https://issues.apache.org/jira/browse/RIVER-337)
* River-332: [Use of Depreciated Interface
java.rmi.server.RemoteCall](https://issues.apache.org/jira/browse/RIVER-332)
-* Updated documentation and tools for new River developers and developers
using River
\ No newline at end of file
+* Updated documentation and tools for new River developers and developers
using River
Modified: river/site/trunk/content/user-guide-river-jar-artifacts.mdtext
URL:
http://svn.apache.org/viewvc/river/site/trunk/content/user-guide-river-jar-artifacts.mdtext?rev=1370723&r1=1370722&r2=1370723&view=diff
==============================================================================
--- river/site/trunk/content/user-guide-river-jar-artifacts.mdtext (original)
+++ river/site/trunk/content/user-guide-river-jar-artifacts.mdtext Wed Aug 8
10:00:24 2012
@@ -3,11 +3,11 @@ Title: User Guide - River JAR Artifacts
# User Guide - River JAR Artifacts
-The following is an extract from Brian Murphy's
[post](http://mail-archives.apache.org/mod_mbox/incubator-river-dev/201008.mbox/%[email protected]%3e)
on the developer mailing list highlight some of the history behind the
River/Jini JAR artifacts.
+The following is an extract from Brian Murphy's
[post](http://mail-archives.apache.org/mod_mbox/river-dev/201008.mbox/%[email protected]%3e)
on the developer mailing list highlight some of the history behind the
River/Jini JAR artifacts.
... For those who might be wondering about artifacts like jini-core.jar,
jini-ext.jar, sun-util.jar, etc., although there have been previous postings
discussing how they are no longer needed, it might help some of the new folks
on the list to hear a repeat of the history of those artifacts; and why they
should not be used, and why they should probably be removed from the build.
Back in the old jini 2.x release time frame, there was quite a bit of time and
thought put into how the distribution should be re-packaged to address
deployment issues; for example, better modularity, supporting overlays when
upgrading, etc. That work resulted in the current artifact structure we now
see; jsk-platform/jsk-lib/jsk-resources/jsk-dl/<service>/<service>-dl.
But because the team did not want to break existing deployments that relied on
the old jar structure, they decided to also include the old artifacts in the
release; along with a detailed release note explaining the new philosophy and
encouraging folks to move to the new model, and be prepared for the removal of
those old jar files down the road. Unfortunately, due to unforeseen events, the
removal of the old unnecessary jar files never occurred, and people seem to
still be using them (at least, based on postings on the various user lists out
there).
-...
\ No newline at end of file
+...
