[infinispan-issues] [JBoss JIRA] (ISPN-4139) Upgrade Lucene 4 Infinispan Directory to Lucene 4.7.0

[Hardy Ferentschik (JIRA)]

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

Hardy Ferentschik commented on ISPN-4139:
-----------------------------------------

{quote}
Infinispan Query uses Hibernate Search, currently still using 4.5.0. So there are tests in this tree which use Hibernate Search 4.5 in combination with the Lucene Directory too, run with Lucene 3.6.2
{quote}
:-(  Would it not help to extract these Lucene sub modules from the main Infinispan tree? Not only is there an nasty interdependency, but you also need a full Infinispan release in order to get out a new version of the Infinispan Directory (which is required by Search). Why not move Infinispan Directory in its own repo or Hibernate Search? 

{quote}
If you have a plan to fix this issue I'm happy to reassign to you as I've been busy with debugging other Search issues,
{quote}
Ok. Right now, I have also other things I want to finish first. Let's see who gets to it first. We just need to make sure t sync in case either one of us starts working on this.

{quote}
 but be aware of the intricate compatibility requirements. 
{quote}
:-(

                
> Upgrade Lucene 4 Infinispan Directory to Lucene 4.7.0
> -----------------------------------------------------
>
>                 Key: ISPN-4139
>                 URL: https://issues.jboss.org/browse/ISPN-4139
>             Project: Infinispan
>          Issue Type: Task
>          Components: Lucene Directory
>            Reporter: Hardy Ferentschik
>            Assignee: Sanne Grinovero
>
> * {{DirectoryLuceneV4}} should not probably extend {{BaseDirectory}} instead of plain {{Directory}}
> * {{Lock#release}} got removed into {{Lock#close}}. {{BaseLuceneLock}} needs to change, but I am not sure how this works in order to support Lucene 3 and 4!?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira