Return-Path: Delivered-To: apmail-jackrabbit-dev-archive@www.apache.org Received: (qmail 65897 invoked from network); 26 Oct 2006 10:21:26 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 26 Oct 2006 10:21:26 -0000 Received: (qmail 41956 invoked by uid 500); 26 Oct 2006 10:21:36 -0000 Delivered-To: apmail-jackrabbit-dev-archive@jackrabbit.apache.org Received: (qmail 41923 invoked by uid 500); 26 Oct 2006 10:21:35 -0000 Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@jackrabbit.apache.org Delivered-To: mailing list dev@jackrabbit.apache.org Received: (qmail 41898 invoked by uid 99); 26 Oct 2006 10:21:35 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 26 Oct 2006 03:21:35 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: local policy) Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 26 Oct 2006 03:21:22 -0700 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 528A77142C2 for ; Thu, 26 Oct 2006 03:20:21 -0700 (PDT) Message-ID: <4830937.1161858021335.JavaMail.root@brutus> Date: Thu, 26 Oct 2006 03:20:21 -0700 (PDT) From: "Jukka Zitting (JIRA)" To: dev@jackrabbit.apache.org Subject: [jira] Commented: (JCR-352) Upgrade to Lucene 2.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ http://issues.apache.org/jira/browse/JCR-352?page=comments#action_12444847 ] Jukka Zitting commented on JCR-352: ----------------------------------- Thanks for the patch! It seems to work fine for me as well. Have you checked with Lucene on whether they're planning to upload the 2.0 dependency in the Maven 1 repository? If not, I can follow up on that. I'd rather not commit the changes until the dependency is there or we've upgraded to Maven 2. It seems that with this change, the ongoing Maven 2 upgrade, the recent PersistenceManager restructuring, and the proposed reintroduction of the great split we would actually be looking at a Jackrabbit 1.2 release sooner than expected. This would mean that we skip the 1.1.1 release. > 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 > Attachments: lucene2-pom.xml.patch, lucene2-project.xml.patch, 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