I'm actually quite happy with that solution for now; with branches I'd have to port each fix and most new features to both.
Ideally we should finish the work to converge the source of tests too, until that is done the tests aren't easy to maintain.
+1
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?On Fri, May 10, 2013 at 11:55 AM, Sanne Grinovero <sanne@infinispan.org> wrote:Following on the idea about CacheStores, I'd like to propose having
the Lucene Directory code to live in its own repository with an
independent release cycle.
Tests-wise it should follow the same policy of the CacheStore: adding
enough tests to the core so that it won't break easily, and in worst
case have the core team jump in to help.
But in this case there is a strong benefit: having the Lucene
Directory to release independently would make it easier to roll out
updates needed by consuming projects which are pinned to the
Infinispan (core) version included in the application server. Most
notably this would break the "circular release dependency" between
Search and Infinispan, and allow quicker innovation in Hibernate
Search while staying compatible with the application server.
Sanne
_______________________________________________
infinispan-dev mailing list
infinispan-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infinispan-dev
_______________________________________________
infinispan-dev mailing list
infinispan-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infinispan-dev