<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Navin,<br>
<br>
6.0 will split core into several jars (names are currently
fictional):<br>
<ul>
<li>infinispan-api (which will only contain interfaces common to
all types of caches)</li>
<li>infinispan-commons (common classes)</li>
<li>infinispan-local (local cache functionality)</li>
<li>infinispan-clustered (clustering functionality)</li>
</ul>
<p>This will make the hotrod client not pull in the entire
embedded infinispan library as well.<br>
One thing this split will cause is that these jars should have
different package roots to avoid the OSGi/JBoss modules "package
split".<br>
</p>
<p>Tristan<br>
</p>
<br>
On 11/22/2012 04:35 AM, Navin Surtani wrote:<br>
</div>
<blockquote
cite="mid:1514219206.14376747.1353555324621.JavaMail.root@redhat.com"
type="cite">
<pre wrap="">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" <a class="moz-txt-link-rfc2396E" href="mailto:ttarrant@redhat.com"><ttarrant@redhat.com></a>
To: "infinispan -Dev List" <a class="moz-txt-link-rfc2396E" href="mailto:infinispan-dev@lists.jboss.org"><infinispan-dev@lists.jboss.org></a>
Cc: "Navin Surtani" <a class="moz-txt-link-rfc2396E" href="mailto:nsurtani@redhat.com"><nsurtani@redhat.com></a>
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
<a class="moz-txt-link-abbreviated" href="mailto:infinispan-dev@lists.jboss.org">infinispan-dev@lists.jboss.org</a>
<a class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/infinispan-dev">https://lists.jboss.org/mailman/listinfo/infinispan-dev</a>
</pre>
</blockquote>
<br>
</body>
</html>