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
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@redhat.com> To: "infinispan -Dev List" <infinispan-dev@lists.jboss.org> Cc: "Navin Surtani" <nsurtani@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@lists.jboss.org https://lists.jboss.org/mailman/listinfo/infinispan-dev