jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jukka Zitting (JIRA)" <j...@apache.org>
Subject [jira] Commented: (JCR-352) Upgrade to Lucene 1.9.1
Date Fri, 17 Mar 2006 22:44:03 GMT
    [ http://issues.apache.org/jira/browse/JCR-352?page=comments#action_12370902 ] 

Jukka Zitting commented on JCR-352:

I tried changing the visibility of the difference() method, which did solve the compile problem,
but now I get a ClassCastException from org.apache.lucene.store.Directory.createFile() when
the repository is being initialized. This problem can be reconstructed like this after placing
lucene/jars/lucene-1.9.1.jar in the local maven repository:

    $ svn export http://svn.apache.org/repos/asf/incubator/jackrabbit/branches/1.0/jackrabbit
    $ cd jackrabbit
    $ perl -i -pe 's/1.4.3/1.9.1/' project.xml
    $ perl -i -pe 's/protected float difference/public float difference/' \
    $ maven test

This seems to have something to do with the "this method should be abstract" notice in the
Lucene Directory.createOutput() method. The FSDirectory class in Jackrabbit doesn't seem to
play well with the modified Directory implementation in Lucene 1.9.1.

If there is a similar simple and non-intrusive fix for this problem, then I can have the change
included in 1.0, otherwise not. In any case I am going to keep Lucene 1.4.3 as the official
dependency in Jackrabbit 1.0. A possible fix would be there just to help people deploy Jackrabbit
1.0 with Lucene 1.9.1.

> Upgrade to Lucene 1.9.1
> -----------------------
>          Key: JCR-352
>          URL: http://issues.apache.org/jira/browse/JCR-352
>      Project: Jackrabbit
>         Type: Improvement
>     Versions: 1.1, 1.0.1, 1.0
>  Environment: All
>     Reporter: Michael Young
>     Assignee: Jukka Zitting

> We would like to upgrade to Lucene 1.9.1. There are jar conflicts when integrating with
other projects such as Liferay Portal --  which uses v 1.9.1.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message