You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@river.apache.org by Peter Firmstone <ji...@zeus.net.au> on 2010/05/11 06:52:13 UTC

Goals & Future Roadmap

Recent Events:

    * 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
      & submitted to svn.
    * New ConcurrentDyamicPolicyProvider in svn.
    * New RevokeablePolicy in svn.


Coming Up:

    * 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.


Some thoughts / comments:

I've created two namespaces under org.apache.river, in order to keep 
separate the API from the implementation:
org.apache.river.api.*
org.apache.river.imp.*

Need some help sorting out ConcurrentDynamicPolicy, some qa tests are 
failing, I'd like some feedback and comments on the failing tests from 
experienced developers if possible.

Need more developers willing to become Apache River committers.

Best Regards,

Peter Firmstone.

Re: Goals & Future Roadmap

Posted by Peter Firmstone <ji...@zeus.net.au>.
Yes definitely, is there a volunteer willing to do the work and 
contribute a patch?

Your contributions will be most welcome.


Jeff Ramsdale wrote:
> Would still be nice to have Maven artifacts. Thanks again for your
> efforts, Peter!
>
> -jeff
>
> On Tue, May 11, 2010 at 12:07 AM, Peter Firmstone <ji...@zeus.net.au> wrote:
>   
>> Anyone got something else they'd like to add?
>>
>> Peter Firmstone wrote:
>>     
>>> Recent Events:
>>>
>>>   * 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
>>>     & submitted to svn.
>>>   * New ConcurrentDyamicPolicyProvider in svn.
>>>   * New RevokeablePolicy in svn.
>>>
>>>
>>> Coming Up:
>>>
>>>   * 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.
>>>
>>>
>>> Some thoughts / comments:
>>>
>>> I've created two namespaces under org.apache.river, in order to keep
>>> separate the API from the implementation:
>>> org.apache.river.api.*
>>> org.apache.river.imp.*
>>>
>>> Need some help sorting out ConcurrentDynamicPolicy, some qa tests are
>>> failing, I'd like some feedback and comments on the failing tests from
>>> experienced developers if possible.
>>>
>>> Need more developers willing to become Apache River committers.
>>>
>>> Best Regards,
>>>
>>> Peter Firmstone.
>>>
>>>
>>>
>>>       
>>     
>
>

Re: Goals & Future Roadmap

Posted by Jeff Ramsdale <je...@gmail.com>.
Would still be nice to have Maven artifacts. Thanks again for your
efforts, Peter!

-jeff

On Tue, May 11, 2010 at 12:07 AM, Peter Firmstone <ji...@zeus.net.au> wrote:
> Anyone got something else they'd like to add?
>
> Peter Firmstone wrote:
>>
>> Recent Events:
>>
>>   * 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
>>     & submitted to svn.
>>   * New ConcurrentDyamicPolicyProvider in svn.
>>   * New RevokeablePolicy in svn.
>>
>>
>> Coming Up:
>>
>>   * 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.
>>
>>
>> Some thoughts / comments:
>>
>> I've created two namespaces under org.apache.river, in order to keep
>> separate the API from the implementation:
>> org.apache.river.api.*
>> org.apache.river.imp.*
>>
>> Need some help sorting out ConcurrentDynamicPolicy, some qa tests are
>> failing, I'd like some feedback and comments on the failing tests from
>> experienced developers if possible.
>>
>> Need more developers willing to become Apache River committers.
>>
>> Best Regards,
>>
>> Peter Firmstone.
>>
>>
>>
>
>

Re: Goals & Future Roadmap

Posted by Peter Firmstone <ji...@zeus.net.au>.
Anyone got something else they'd like to add?

Peter Firmstone wrote:
> Recent Events:
>
>    * 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
>      & submitted to svn.
>    * New ConcurrentDyamicPolicyProvider in svn.
>    * New RevokeablePolicy in svn.
>
>
> Coming Up:
>
>    * 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.
>
>
> Some thoughts / comments:
>
> I've created two namespaces under org.apache.river, in order to keep 
> separate the API from the implementation:
> org.apache.river.api.*
> org.apache.river.imp.*
>
> Need some help sorting out ConcurrentDynamicPolicy, some qa tests are 
> failing, I'd like some feedback and comments on the failing tests from 
> experienced developers if possible.
>
> Need more developers willing to become Apache River committers.
>
> Best Regards,
>
> Peter Firmstone.
>
>
>