[infinispan-issues] [JBoss JIRA] (ISPN-6252) Upgrade to Apache Lucene 5.5

[Sanne Grinovero (JIRA)]

    [ https://issues.jboss.org/browse/ISPN-6252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13169673#comment-13169673 ] 

Sanne Grinovero commented on ISPN-6252:
---------------------------------------

yes, right.
To be clear: I'm not solely concerned about which *version* is being used by the two projects, they also need to be using the same instance of the module at runtime.
So if both products are packaging the same version but use a different module slot, they would still not be compatible.

Wondering if we should go "all in" and also separate the Lucene Directory: we could have a single source code module by  targeting the same Lucene version, but then package it in two different modules so they can refer to the different slots.

> 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)