[infinispan-dev] ISPN-2463: Hopefully one final question

Manik Surtani manik at jboss.org
Thu Nov 22 12:02:31 EST 2012


And this will also determine where the tests live.  I think we'll end up with a situation where the existing test suite is broken up and scattered across the different modules.

On 22 Nov 2012, at 09:56, Tristan Tarrant <ttarrant at redhat.com> wrote:

> Navin,
> 
> 6.0 will split core into several jars (names are currently fictional):
> infinispan-api (which will only contain interfaces common to all types of caches)
> infinispan-commons (common classes)
> infinispan-local (local cache functionality)
> infinispan-clustered (clustering functionality)
> This will make the hotrod client not pull in the entire embedded infinispan library as well.
> One thing this split will cause is that these jars should have different package roots to avoid the OSGi/JBoss modules "package split".
> Tristan
> 
> On 11/22/2012 04:35 AM, Navin Surtani wrote:
>> Could you elaborate on what other refactoring has to be done please? I mean, specifically on the configuration side, if there's a 1-for-1 replacement in terms of the configuration that's already available then shouldn't we just be directly swapping in the other API? I get that there are some changes to the way that things would be configured, and some defaults have been changed - but there are still ways to do the same thing correct?
>> 
>> 
>> ------------------------ 
>> Navin Surtani 
>> 
>> 
>> Software Engineer 
>> JBoss SET 
>> JBoss EAP 
>> 
>> 
>> Twitter: @navssurtani 
>> 
>> ----- Original Message -----
>> From: "Tristan Tarrant" <ttarrant at redhat.com>
>> To: "infinispan -Dev List" <infinispan-dev at lists.jboss.org>
>> Cc: "Navin Surtani" <nsurtani at redhat.com>
>> Sent: Wednesday, November 21, 2012 8:56:20 PM
>> Subject: Re: [infinispan-dev] ISPN-2463: Hopefully one final question
>> 
>> Before applying the chainsaw, we must first decide if we're going to 
>> have a 5.3.
>> Also 6.0 will have much more refactoring than just dropping 
>> org.infinispan.config.* so I think that should be handled first.
>> 
>> Tristan
>> _______________________________________________
>> infinispan-dev mailing list
>> infinispan-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/infinispan-dev
>> 
> 
> _______________________________________________
> infinispan-dev mailing list
> infinispan-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/infinispan-dev

--
Manik Surtani
manik at jboss.org
twitter.com/maniksurtani

Platform Architect, JBoss Data Grid
http://red.ht/data-grid

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/infinispan-dev/attachments/20121122/593079f7/attachment.html 


More information about the infinispan-dev mailing list