Re: [infinispan-dev] Splitting the Lucene Directory in its own top-level project

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(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/infinispan-dev