<div dir="ltr">+1<br><br>Would that mean that you could change the lucene-v3 and lucene-v4 modules to be different branches in the new repository instead? Or would you even want to do that?<br></div><div class="gmail_extra">
<br><br><div class="gmail_quote">On Fri, May 10, 2013 at 11:55 AM, Sanne Grinovero <span dir="ltr"><<a href="mailto:sanne@infinispan.org" target="_blank">sanne@infinispan.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Following on the idea about CacheStores, I'd like to propose having<br>
the Lucene Directory code to live in its own repository with an<br>
independent release cycle.<br>
<br>
Tests-wise it should follow the same policy of the CacheStore: adding<br>
enough tests to the core so that it won't break easily, and in worst<br>
case have the core team jump in to help.<br>
<br>
But in this case there is a strong benefit: having the Lucene<br>
Directory to release independently would make it easier to roll out<br>
updates needed by consuming projects which are pinned to the<br>
Infinispan (core) version included in the application server. Most<br>
notably this would break the "circular release dependency" between<br>
Search and Infinispan, and allow quicker innovation in Hibernate<br>
Search while staying compatible with the application server.<br>
<br>
Sanne<br>
_______________________________________________<br>
infinispan-dev mailing list<br>
<a href="mailto:infinispan-dev@lists.jboss.org">infinispan-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/infinispan-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/infinispan-dev</a><br>
</blockquote></div><br></div>