Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Message-ID: <31502823.1165951347295.JavaMail.jira@brutus>
Date: Tue, 12 Dec 2006 11:22:27 -0800 (PST)
From: "Jukka Zitting (JIRA)" <jira@apache.org>
To: dev@jackrabbit.apache.org
Subject: [jira] Resolved: (JCR-352) Upgrade to Lucene 2.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

     [ http://issues.apache.org/jira/browse/JCR-352?page=all ]

Jukka Zitting resolved JCR-352.
-------------------------------

    Resolution: Fixed

Committed the latest patch in revision 486281. Like with the Derby upgrade (JCR-610), Lucene 2.0 is backwards compatible with indexes created with version 1.4.x.  Thus there should be no need for manual upgrade procedures.

Thanks Przemo and everyone else who participated in this!

> Upgrade to Lucene 2.0
> ---------------------
>
>                 Key: JCR-352
>                 URL: http://issues.apache.org/jira/browse/JCR-352
>             Project: Jackrabbit
>          Issue Type: Improvement
>          Components: indexing
>    Affects Versions: 1.0, 0.9, 1.0.1
>         Environment: All
>            Reporter: Michael Young
>         Assigned To: Jukka Zitting
>            Priority: Minor
>             Fix For: 1.2
>
>         Attachments: lucene2-pom.xml.patch, lucene2-project.xml.patch, lucene2.patch, updated-lucene2.patch
>
>
> 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: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira