river-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bryan Thompson <br...@systap.com>
Subject Re: New Chair for Apache River PMC
Date Tue, 13 May 2014 12:46:45 GMT
Sounds good. 

> On May 13, 2014, at 8:25 AM, Rafał Krupiński <rafal.krupinski@sorcersoft.com>
wrote:
> 
> Dnia wtorek, 13 maja 2014 08:11:21 Bryan Thompson pisze:
>> Is the name change a requirement for a 3.0?  The problem is that this will
>> break compatibility making it extremely difficult to establish performance
>> in existing applications while preserving the ability to rollback to a
>> known good code base.  I would have to give a -1 to this.  We need to
>> validate the release against running systems before changing the
>> namespaces.  If that means keeping this a 2.x release, that's fine.
> 
> Change namespaces can be made in a compatible way. There could be additional 
> jars with empty classes in the old packages that would just extend the classes 
> in the new packages, like below:
> 
> //some-module.jar
> org.apache.river.SimeClass{
> //class moved from net.jini
> }
> 
> //some-module-compat.jar (that depends on some-module.jar)
> net.jini.SomeClass extends org.apache.river.SomeClass{
> //empty class
> }
> 
> In order to migrate to the new version, you'd need to replace the actual 
> module and add the compatibility module.
> 
> Regards
> Rafał

Mime
View raw message