<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hey!<br>
<br>
After several discussions we decided to create 2 separate modules
for Spring 3 and Spring 4 support. <br>
<br>
As Gustavo mentioned, there are a lot of new things in Spring 4.1
which are connected to caching. Once we start supporting Spring 3
and 4 integration using the same jar - new features might be hard
(if not impossible) to introduce. Having 2 separate jars gives us
flexibility which might be useful in the future.<br>
<br>
The code might be found here: <b><a class="moz-txt-link-freetext" href="https://github.com/infinispan/infinispan/pull/2957">https://github.com/infinispan/infinispan/pull/2957</a></b><br>
<br>
Best regards<br>
Sebastian<br>
<br>
<br>
<div class="moz-cite-prefix">On 10/14/2014 03:41 PM, Gustavo
Fernandes wrote:<br>
</div>
<blockquote
cite="mid:CAAV25CFx8PZ7KvAziQLC=Zc+vP7fwsJZ570-A0FRH_bRg0jL0g@mail.gmail.com"
type="cite">
<pre wrap="">I prefer #1, since it decouples Spring 3 from Spring 4. For example,
Spring 4.1 is bringing many improvements on Cache [1], which I'm not
sure if it will available on 3.2.x maintenance branch.
[1] <a class="moz-txt-link-freetext" href="http://spring.io/blog/2014/06/16/further-cache-improvements-in-spring-4-1">http://spring.io/blog/2014/06/16/further-cache-improvements-in-spring-4-1</a>
<a class="moz-txt-link-rfc2396E" href="mailto:slaskawi@redhat.com"><slaskawi@redhat.com></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">
1. Create copy of Spring 3 module and put everything into newly created
Spring 4, then update versions and implement new methods in Cache
interface.
Pros:
- 1 OSGi bundle - transparent upgrade - just replace spring bundle
- Easy to maintain Spring 4 only fixes
Cons:
- Code duplication
</pre>
</blockquote>
</blockquote>
<br>
</body>
</html>