river-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tom Hobbs <tvho...@googlemail.com>
Subject Re: Release: Making Delgates and reference Collections separate libraries
Date Thu, 23 Feb 2012 09:21:41 GMT
Does anyone know the criteria for defining sub projects?  We seem to have a
couple of them now, including the Scala and easy config stuff I'm working
on.

Maybe there's a task to setup a couple of these all in one go.

Sent via mobile device, please forgive typos and spacing errors.

On 22 Feb 2012 23:41, "Peter Firmstone" <peter.firmstone@zeus.net.au> wrote:

> **
> I'm removing delgate implementations from apache river, in preparation for
> release, they cannot support compilation on both java 6 and 7 with the same
> source code.   Delegates depend on reference collections, there's also some
> common security stuff, that could be broken out separately that Delegates
> require, eg PermissionComparator.
>
> I propose three separate libraries, that can exist independantly of River
> releases:
>
>    1. reference-collections
>    2. delegates (depends on reference-collections and
>    PermissionComparator).
>     3. concurrent policy file provider, including PermissionComparator.
>
> I've attached the public api for reference collections (this is my own
> local copy, it's AL2 licensed, it's a better documented than the copy in
> trunk at present), we can change the package path names later after we
> decide a suitable name, I'm thinking we might need to create a libs
> subproject for this stuff on svn.
>
> Cheers,
>
> Peter.
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message