You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@river.apache.org by Tom Hobbs <tv...@googlemail.com> on 2010/08/23 17:13:49 UTC
River Status Update
As discussed, there's a blurb and the end of this email which I intend to
(somehow) get onto the River main web page as a bit of an update. Does
anyone have any thoughts? I've shamelessly enhanced (read: stolen) the
contents of Peter's status email from Tue, 11 May 2010 "Goals & Future
Roadmap".
The list of Jira issues at the end is ordered by "last edited" according to
the issue and was limited by my attention span looking through Jira. Is
there anything on there that shouldn't be? What big ones did I miss?
@Benson, is this this kind of thing you were talking about?
Cheers,
Tom
River is starting to gain some momentum and is seeing increasing activity on
it's developer mailing list. Lots of code and ideas are being thrown around
with some interesting discussions and some great code being produced. Add a
new Apache Mentor into the mix and the project is starting to look like it
could shape up for graduation soon...
Recent River event include:
* River 2.1.2 has been released
* New CodebaseAccessClassLoader and accociated changes submitted to svn
(Thanks to Gregg Wonderly)
* New StreamServiceRegistrar Interface and other additions proposed
and submitted to svn
* New ConcurrentDyamicPolicyProvider in svn
* New RevokeablePolicy in svn
New functionality and fixes in the pipeline include:
* New Groovy Configuration System (Thanks to Dennis Reedy)
* Fully functional ConcurrentDynamicPolicyProvider
* Fully functional RevokeablePolicy
* A StreamServiceRegistrar implementation
Future Roadmap:
* Integrate Jini Surrogate Architecture.
* Apache River - Java CDC support for dynamic code downloading and Jini
Services utilising a subset of Jini's API.
* Apache River 2.2.0 Release, Scheduled for December.
* Better "Getting starting" documentation for new River developers
* Better resources for users of River (Thanks to Tim Blackman for
Jini-in-a-Jar donation)
River is actively looking for people who can help with the following areas:
* Revi1ew of patches waiting to be included into SVN, particularly
- River-345: SDM LookupCache multi-LUS stale proxy/discard problems (
https://issues.apache.org/jira/browse/RIVER-345)
- River-336: Jini should support platforms other than those with
RMIClassLoader as the classloading control point. IDEs inparticular need
help (https://issues.apache.org/jira/browse/RIVER-336)
- River-313: Provide mechanism to swap in alternatives to Java DSL for
service configuration (https://issues.apache.org/jira/browse/RIVER-313)
* New feature functionality, particularly
- 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
Re: River Status Update
Posted by Peter Firmstone <ji...@zeus.net.au>.
Thanks Tom, no worries,
The Revocable Policy is experimental, so we probably shouldn't guarantee
that it'll be included. We still need to implement Security Delegates
before it'll be effective. This will require lots of testing and
feedback before it makes a release.
We certainly could use some more feedback on the
StreamServiceRegistrar's proposed interface before we start implementing
it. It's intended for delayed unmarshalling and handling very large
lookup result sets.
Regards,
Peter.
Tom Hobbs wrote:
> As discussed, there's a blurb and the end of this email which I intend to
> (somehow) get onto the River main web page as a bit of an update. Does
> anyone have any thoughts? I've shamelessly enhanced (read: stolen) the
> contents of Peter's status email from Tue, 11 May 2010 "Goals & Future
> Roadmap".
>
> The list of Jira issues at the end is ordered by "last edited" according to
> the issue and was limited by my attention span looking through Jira. Is
> there anything on there that shouldn't be? What big ones did I miss?
>
> @Benson, is this this kind of thing you were talking about?
>
> Cheers,
>
> Tom
>
>
>
> River is starting to gain some momentum and is seeing increasing activity on
> it's developer mailing list. Lots of code and ideas are being thrown around
> with some interesting discussions and some great code being produced. Add a
> new Apache Mentor into the mix and the project is starting to look like it
> could shape up for graduation soon...
>
> Recent River event include:
>
> * River 2.1.2 has been released
> * New CodebaseAccessClassLoader and accociated changes submitted to svn
> (Thanks to Gregg Wonderly)
> * New StreamServiceRegistrar Interface and other additions proposed
> and submitted to svn
> * New ConcurrentDyamicPolicyProvider in svn
> * New RevokeablePolicy in svn
>
> New functionality and fixes in the pipeline include:
>
> * New Groovy Configuration System (Thanks to Dennis Reedy)
> * Fully functional ConcurrentDynamicPolicyProvider
> * Fully functional RevokeablePolicy
> * A StreamServiceRegistrar implementation
>
> Future Roadmap:
>
> * Integrate Jini Surrogate Architecture.
> * Apache River - Java CDC support for dynamic code downloading and Jini
> Services utilising a subset of Jini's API.
> * Apache River 2.2.0 Release, Scheduled for December.
> * Better "Getting starting" documentation for new River developers
> * Better resources for users of River (Thanks to Tim Blackman for
> Jini-in-a-Jar donation)
>
> River is actively looking for people who can help with the following areas:
>
> * Revi1ew of patches waiting to be included into SVN, particularly
> - River-345: SDM LookupCache multi-LUS stale proxy/discard problems (
> https://issues.apache.org/jira/browse/RIVER-345)
> - River-336: Jini should support platforms other than those with
> RMIClassLoader as the classloading control point. IDEs inparticular need
> help (https://issues.apache.org/jira/browse/RIVER-336)
> - River-313: Provide mechanism to swap in alternatives to Java DSL for
> service configuration (https://issues.apache.org/jira/browse/RIVER-313)
> * New feature functionality, particularly
> - 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
>
>
Re: River Status Update
Posted by Benson Margulies <bi...@gmail.com>.
Confluence edits should appear on their own -- after some period of
time. If they don't, well have to ask for more advice.
On Tue, Aug 24, 2010 at 11:24 AM, Sim IJskes - QCG <si...@qcg.nl> wrote:
> On 08/24/2010 04:58 PM, Benson Margulies wrote:
>>
>> I'm very sorry to be a source of confusion here. I tripped over some
>> ancient static web site source for River, so I concluded that it was
>> not already in Confluence. It is already in Confluence, and all you
>> committers should have access to edit it.
>
> Could you tell me how we sync the website and confluence? I've changed some
> page once, and the website wasn't updated.
>
> Gr. Sim
>
>
Re: River Status Update
Posted by Sim IJskes - QCG <si...@qcg.nl>.
On 08/24/2010 04:58 PM, Benson Margulies wrote:
> I'm very sorry to be a source of confusion here. I tripped over some
> ancient static web site source for River, so I concluded that it was
> not already in Confluence. It is already in Confluence, and all you
> committers should have access to edit it.
Could you tell me how we sync the website and confluence? I've changed
some page once, and the website wasn't updated.
Gr. Sim
Re: River Status Update
Posted by Benson Margulies <bi...@gmail.com>.
I'm very sorry to be a source of confusion here. I tripped over some
ancient static web site source for River, so I concluded that it was
not already in Confluence. It is already in Confluence, and all you
committers should have access to edit it.
On Tue, Aug 24, 2010 at 9:18 AM, Tom Hobbs <tv...@googlemail.com> wrote:
> Sorry for being daft, but what does "ask for the required Confluence karma"
> mean?
>
> Thanks.
>
>
> On Tue, Aug 24, 2010 at 12:43 PM, Benson Margulies <bi...@gmail.com>wrote:
>
>> OK here.
>>
>> On Tue, Aug 24, 2010 at 5:33 AM, Tom Hobbs <tv...@googlemail.com> wrote:
>> > Thanks for the help on process, guys.
>> >
>> > Does anyone have any comments on the content?
>> >
>> >
>> > On Tue, Aug 24, 2010 at 2:48 AM, Benson Margulies <bimargulies@gmail.com
>> >wrote:
>> >
>> >> Niclas is correct. To my partial shock and horror (just kidding), the
>> >> entire incubator web site is One Big Thing, and you run a build on the
>> >> whole business.
>> >>
>> >> http://incubator.apache.org/guides/website.html
>> >>
>> >> I just discovered that I myself am not in the necessary group to
>> >> complete the process, and I opened a ticket with infra.
>> >>
>> >> On Mon, Aug 23, 2010 at 8:32 PM, Niclas Hedhman <ni...@hedhman.org>
>> >> wrote:
>> >> > On Tue, Aug 24, 2010 at 12:07 AM, Benson Margulies
>> >> > <bi...@gmail.com> wrote:
>> >> >> Two things to hit:
>> >> >>
>> >> >>
>> >>
>> https://svn.apache.org/repos/asf/incubator/public/trunk/site-author/projects/river.xml
>> >> >>
>> >> >> http://svn.apache.org/repos/asf/incubator/river/site/
>> >> >>
>> >> >> It looks to me as if the former is magically self-transforming into
>> >> >> HTML, and the later you modify, commit, build, and stick into the
>> >> >> right place in /www on people.apache.org.
>> >> >
>> >> > Does it now? I have been out of the loop for long, as we have "always"
>> >> > needed to both "build" the site-author with the build script in its
>> >> > parent directory as well as "publish" it to /www.
>> >> >
>> >> > It is also important to know that there can be substantial delays,
>> >> > since website is mirrored somehow.
>> >> >
>> >> >
>> >> > Cheers
>> >> > --
>> >> > Niclas Hedhman, Software Developer
>> >> > http://www.qi4j.org - New Energy for Java
>> >> >
>> >> > I live here; http://tinyurl.com/2qq9er
>> >> > I work here; http://tinyurl.com/2ymelc
>> >> > I relax here; http://tinyurl.com/2cgsug
>> >> >
>> >>
>> >
>>
>
Re: River Status Update
Posted by Tom Hobbs <tv...@googlemail.com>.
Sorry for being daft, but what does "ask for the required Confluence karma"
mean?
Thanks.
On Tue, Aug 24, 2010 at 12:43 PM, Benson Margulies <bi...@gmail.com>wrote:
> OK here.
>
> On Tue, Aug 24, 2010 at 5:33 AM, Tom Hobbs <tv...@googlemail.com> wrote:
> > Thanks for the help on process, guys.
> >
> > Does anyone have any comments on the content?
> >
> >
> > On Tue, Aug 24, 2010 at 2:48 AM, Benson Margulies <bimargulies@gmail.com
> >wrote:
> >
> >> Niclas is correct. To my partial shock and horror (just kidding), the
> >> entire incubator web site is One Big Thing, and you run a build on the
> >> whole business.
> >>
> >> http://incubator.apache.org/guides/website.html
> >>
> >> I just discovered that I myself am not in the necessary group to
> >> complete the process, and I opened a ticket with infra.
> >>
> >> On Mon, Aug 23, 2010 at 8:32 PM, Niclas Hedhman <ni...@hedhman.org>
> >> wrote:
> >> > On Tue, Aug 24, 2010 at 12:07 AM, Benson Margulies
> >> > <bi...@gmail.com> wrote:
> >> >> Two things to hit:
> >> >>
> >> >>
> >>
> https://svn.apache.org/repos/asf/incubator/public/trunk/site-author/projects/river.xml
> >> >>
> >> >> http://svn.apache.org/repos/asf/incubator/river/site/
> >> >>
> >> >> It looks to me as if the former is magically self-transforming into
> >> >> HTML, and the later you modify, commit, build, and stick into the
> >> >> right place in /www on people.apache.org.
> >> >
> >> > Does it now? I have been out of the loop for long, as we have "always"
> >> > needed to both "build" the site-author with the build script in its
> >> > parent directory as well as "publish" it to /www.
> >> >
> >> > It is also important to know that there can be substantial delays,
> >> > since website is mirrored somehow.
> >> >
> >> >
> >> > Cheers
> >> > --
> >> > Niclas Hedhman, Software Developer
> >> > http://www.qi4j.org - New Energy for Java
> >> >
> >> > I live here; http://tinyurl.com/2qq9er
> >> > I work here; http://tinyurl.com/2ymelc
> >> > I relax here; http://tinyurl.com/2cgsug
> >> >
> >>
> >
>
Re: River Status Update
Posted by Benson Margulies <bi...@gmail.com>.
OK here.
On Tue, Aug 24, 2010 at 5:33 AM, Tom Hobbs <tv...@googlemail.com> wrote:
> Thanks for the help on process, guys.
>
> Does anyone have any comments on the content?
>
>
> On Tue, Aug 24, 2010 at 2:48 AM, Benson Margulies <bi...@gmail.com>wrote:
>
>> Niclas is correct. To my partial shock and horror (just kidding), the
>> entire incubator web site is One Big Thing, and you run a build on the
>> whole business.
>>
>> http://incubator.apache.org/guides/website.html
>>
>> I just discovered that I myself am not in the necessary group to
>> complete the process, and I opened a ticket with infra.
>>
>> On Mon, Aug 23, 2010 at 8:32 PM, Niclas Hedhman <ni...@hedhman.org>
>> wrote:
>> > On Tue, Aug 24, 2010 at 12:07 AM, Benson Margulies
>> > <bi...@gmail.com> wrote:
>> >> Two things to hit:
>> >>
>> >>
>> https://svn.apache.org/repos/asf/incubator/public/trunk/site-author/projects/river.xml
>> >>
>> >> http://svn.apache.org/repos/asf/incubator/river/site/
>> >>
>> >> It looks to me as if the former is magically self-transforming into
>> >> HTML, and the later you modify, commit, build, and stick into the
>> >> right place in /www on people.apache.org.
>> >
>> > Does it now? I have been out of the loop for long, as we have "always"
>> > needed to both "build" the site-author with the build script in its
>> > parent directory as well as "publish" it to /www.
>> >
>> > It is also important to know that there can be substantial delays,
>> > since website is mirrored somehow.
>> >
>> >
>> > Cheers
>> > --
>> > Niclas Hedhman, Software Developer
>> > http://www.qi4j.org - New Energy for Java
>> >
>> > I live here; http://tinyurl.com/2qq9er
>> > I work here; http://tinyurl.com/2ymelc
>> > I relax here; http://tinyurl.com/2cgsug
>> >
>>
>
Re: River Status Update
Posted by Tom Hobbs <tv...@googlemail.com>.
Thanks for the help on process, guys.
Does anyone have any comments on the content?
On Tue, Aug 24, 2010 at 2:48 AM, Benson Margulies <bi...@gmail.com>wrote:
> Niclas is correct. To my partial shock and horror (just kidding), the
> entire incubator web site is One Big Thing, and you run a build on the
> whole business.
>
> http://incubator.apache.org/guides/website.html
>
> I just discovered that I myself am not in the necessary group to
> complete the process, and I opened a ticket with infra.
>
> On Mon, Aug 23, 2010 at 8:32 PM, Niclas Hedhman <ni...@hedhman.org>
> wrote:
> > On Tue, Aug 24, 2010 at 12:07 AM, Benson Margulies
> > <bi...@gmail.com> wrote:
> >> Two things to hit:
> >>
> >>
> https://svn.apache.org/repos/asf/incubator/public/trunk/site-author/projects/river.xml
> >>
> >> http://svn.apache.org/repos/asf/incubator/river/site/
> >>
> >> It looks to me as if the former is magically self-transforming into
> >> HTML, and the later you modify, commit, build, and stick into the
> >> right place in /www on people.apache.org.
> >
> > Does it now? I have been out of the loop for long, as we have "always"
> > needed to both "build" the site-author with the build script in its
> > parent directory as well as "publish" it to /www.
> >
> > It is also important to know that there can be substantial delays,
> > since website is mirrored somehow.
> >
> >
> > Cheers
> > --
> > Niclas Hedhman, Software Developer
> > http://www.qi4j.org - New Energy for Java
> >
> > I live here; http://tinyurl.com/2qq9er
> > I work here; http://tinyurl.com/2ymelc
> > I relax here; http://tinyurl.com/2cgsug
> >
>
Re: River Status Update
Posted by Jukka Zitting <ju...@gmail.com>.
Hi,
On Tue, Aug 24, 2010 at 9:37 AM, Sim IJskes - QCG <si...@qcg.nl> wrote:
> Why not takedown the current site, and redirect to confluence?
This is about the River status page [1] that's maintained as a part of
the main Incubator site.
The River web site at [2] is maintained in our Confluence wiki at [3].
All River committers are given full edit access to the wiki. You just
need to register an account and ask for the required Confluence karma.
PS. The status update Tom started will provide excellent material for
the next River status report that's due in September [4].
[1] http://incubator.apache.org/projects/river.html
[2] http://incubator.apache.org/river/
[3] https://cwiki.apache.org/confluence/display/RIVER
[4] http://wiki.apache.org/incubator/September2010
BR,
Jukka Zitting
Re: River Status Update
Posted by Sim IJskes - QCG <si...@qcg.nl>.
On 08/24/2010 03:48 AM, Benson Margulies wrote:
> Niclas is correct. To my partial shock and horror (just kidding), the
> entire incubator web site is One Big Thing, and you run a build on the
> whole business.
Why not takedown the current site, and redirect to confluence?
We can easily prototype the pages there.
Gr. Sim
Re: River Status Update
Posted by Craig L Russell <cr...@oracle.com>.
On Aug 23, 2010, at 6:48 PM, Benson Margulies wrote:
> Niclas is correct.
Waaaay more often than not.
Craig
Craig L Russell
Architect, Oracle
http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@oracle.com
P.S. A good JDO? O, Gasp!
Re: River Status Update
Posted by Benson Margulies <bi...@gmail.com>.
Niclas is correct. To my partial shock and horror (just kidding), the
entire incubator web site is One Big Thing, and you run a build on the
whole business.
http://incubator.apache.org/guides/website.html
I just discovered that I myself am not in the necessary group to
complete the process, and I opened a ticket with infra.
On Mon, Aug 23, 2010 at 8:32 PM, Niclas Hedhman <ni...@hedhman.org> wrote:
> On Tue, Aug 24, 2010 at 12:07 AM, Benson Margulies
> <bi...@gmail.com> wrote:
>> Two things to hit:
>>
>> https://svn.apache.org/repos/asf/incubator/public/trunk/site-author/projects/river.xml
>>
>> http://svn.apache.org/repos/asf/incubator/river/site/
>>
>> It looks to me as if the former is magically self-transforming into
>> HTML, and the later you modify, commit, build, and stick into the
>> right place in /www on people.apache.org.
>
> Does it now? I have been out of the loop for long, as we have "always"
> needed to both "build" the site-author with the build script in its
> parent directory as well as "publish" it to /www.
>
> It is also important to know that there can be substantial delays,
> since website is mirrored somehow.
>
>
> Cheers
> --
> Niclas Hedhman, Software Developer
> http://www.qi4j.org - New Energy for Java
>
> I live here; http://tinyurl.com/2qq9er
> I work here; http://tinyurl.com/2ymelc
> I relax here; http://tinyurl.com/2cgsug
>
Re: River Status Update
Posted by Benson Margulies <bi...@gmail.com>.
I looked for a build script and didn't see it, but that's probably
because I'm an idiot.
On Mon, Aug 23, 2010 at 8:32 PM, Niclas Hedhman <ni...@hedhman.org> wrote:
> On Tue, Aug 24, 2010 at 12:07 AM, Benson Margulies
> <bi...@gmail.com> wrote:
>> Two things to hit:
>>
>> https://svn.apache.org/repos/asf/incubator/public/trunk/site-author/projects/river.xml
>>
>> http://svn.apache.org/repos/asf/incubator/river/site/
>>
>> It looks to me as if the former is magically self-transforming into
>> HTML, and the later you modify, commit, build, and stick into the
>> right place in /www on people.apache.org.
>
> Does it now? I have been out of the loop for long, as we have "always"
> needed to both "build" the site-author with the build script in its
> parent directory as well as "publish" it to /www.
>
> It is also important to know that there can be substantial delays,
> since website is mirrored somehow.
>
>
> Cheers
> --
> Niclas Hedhman, Software Developer
> http://www.qi4j.org - New Energy for Java
>
> I live here; http://tinyurl.com/2qq9er
> I work here; http://tinyurl.com/2ymelc
> I relax here; http://tinyurl.com/2cgsug
>
Re: River Status Update
Posted by Niclas Hedhman <ni...@hedhman.org>.
On Tue, Aug 24, 2010 at 12:07 AM, Benson Margulies
<bi...@gmail.com> wrote:
> Two things to hit:
>
> https://svn.apache.org/repos/asf/incubator/public/trunk/site-author/projects/river.xml
>
> http://svn.apache.org/repos/asf/incubator/river/site/
>
> It looks to me as if the former is magically self-transforming into
> HTML, and the later you modify, commit, build, and stick into the
> right place in /www on people.apache.org.
Does it now? I have been out of the loop for long, as we have "always"
needed to both "build" the site-author with the build script in its
parent directory as well as "publish" it to /www.
It is also important to know that there can be substantial delays,
since website is mirrored somehow.
Cheers
--
Niclas Hedhman, Software Developer
http://www.qi4j.org - New Energy for Java
I live here; http://tinyurl.com/2qq9er
I work here; http://tinyurl.com/2ymelc
I relax here; http://tinyurl.com/2cgsug
Re: River Status Update
Posted by Benson Margulies <bi...@gmail.com>.
Two things to hit:
https://svn.apache.org/repos/asf/incubator/public/trunk/site-author/projects/river.xml
http://svn.apache.org/repos/asf/incubator/river/site/
It looks to me as if the former is magically self-transforming into
HTML, and the later you modify, commit, build, and stick into the
right place in /www on people.apache.org.
On Mon, Aug 23, 2010 at 11:13 AM, Tom Hobbs <tv...@googlemail.com> wrote:
> As discussed, there's a blurb and the end of this email which I intend to
> (somehow) get onto the River main web page as a bit of an update. Does
> anyone have any thoughts? I've shamelessly enhanced (read: stolen) the
> contents of Peter's status email from Tue, 11 May 2010 "Goals & Future
> Roadmap".
>
> The list of Jira issues at the end is ordered by "last edited" according to
> the issue and was limited by my attention span looking through Jira. Is
> there anything on there that shouldn't be? What big ones did I miss?
>
> @Benson, is this this kind of thing you were talking about?
>
> Cheers,
>
> Tom
>
>
>
> River is starting to gain some momentum and is seeing increasing activity on
> it's developer mailing list. Lots of code and ideas are being thrown around
> with some interesting discussions and some great code being produced. Add a
> new Apache Mentor into the mix and the project is starting to look like it
> could shape up for graduation soon...
>
> Recent River event include:
>
> * River 2.1.2 has been released
> * New CodebaseAccessClassLoader and accociated changes submitted to svn
> (Thanks to Gregg Wonderly)
> * New StreamServiceRegistrar Interface and other additions proposed
> and submitted to svn
> * New ConcurrentDyamicPolicyProvider in svn
> * New RevokeablePolicy in svn
>
> New functionality and fixes in the pipeline include:
>
> * New Groovy Configuration System (Thanks to Dennis Reedy)
> * Fully functional ConcurrentDynamicPolicyProvider
> * Fully functional RevokeablePolicy
> * A StreamServiceRegistrar implementation
>
> Future Roadmap:
>
> * Integrate Jini Surrogate Architecture.
> * Apache River - Java CDC support for dynamic code downloading and Jini
> Services utilising a subset of Jini's API.
> * Apache River 2.2.0 Release, Scheduled for December.
> * Better "Getting starting" documentation for new River developers
> * Better resources for users of River (Thanks to Tim Blackman for
> Jini-in-a-Jar donation)
>
> River is actively looking for people who can help with the following areas:
>
> * Revi1ew of patches waiting to be included into SVN, particularly
> - River-345: SDM LookupCache multi-LUS stale proxy/discard problems (
> https://issues.apache.org/jira/browse/RIVER-345)
> - River-336: Jini should support platforms other than those with
> RMIClassLoader as the classloading control point. IDEs inparticular need
> help (https://issues.apache.org/jira/browse/RIVER-336)
> - River-313: Provide mechanism to swap in alternatives to Java DSL for
> service configuration (https://issues.apache.org/jira/browse/RIVER-313)
> * New feature functionality, particularly
> - 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
>