[
https://issues.jboss.org/browse/ISPN-6252?page=com.atlassian.jira.plugin....
]
Gustavo Fernandes commented on ISPN-6252:
-----------------------------------------
So there are two ways of tacking this I can think of:
* The Infinispan module build consumes hibernate search module, but manipulate it to
replace the internal Lucene version. This is a bit brittle.
* Publish \[1\] and Hibernate Search depends on this module via an alias slot, like
"lucene-slot". On Infinispan side, we consume
hibernate search module but filter out the alias and use our own alias to a different
lucene version, also coming from \[1\]
Thoughts?
\[1\]
https://github.com/hibernate/lucene-modules
Upgrade to Apache Lucene 5.5
----------------------------
Key: ISPN-6252
URL:
https://issues.jboss.org/browse/ISPN-6252
Project: Infinispan
Issue Type: Component Upgrade
Components: Embedded Querying
Reporter: Sanne Grinovero
Assignee: Gustavo Fernandes
Fix For: 8.2.0.CR1
Apache Lucene 5.5 is released now, and is "drop-in compatible" with versions
5.3 and 5.4 so you don't have to wait for an Hibernate Search release.
It's also being the last one for the 5.x series before 6, so I expect that we'll
see some more micro releases for maintenance but essentially that this will be some form
of long term commitment.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)