|
|
|
|
|
|
I'm refactoring the Infinispan integration module better isolate the classpath of this integration module from the rest of Search (it is currently leaking many jars into visibility of Search).
This module was always meant to make it possible to swap in a dependency of different versions of Infinispan than the one normally included in the application server, but the current module layout is rather leaky it seems; this might conflict with the Infinispan version used by Hibernate ORM and needs to be isolated, but we still want to be able to start it by loading custom resources (configuration files).
This relates to:
- http://lists.jboss.org/pipermail/hibernate-dev/2014-October/011825.html
- http://lists.jboss.org/pipermail/infinispan-dev/2014-October/015549.html
|
|
|
|
|
|
