Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Message-ID: <22337689.1165838185247.JavaMail.jira@brutus>
Date: Mon, 11 Dec 2006 03:56:25 -0800 (PST)
From: "Jukka Zitting (JIRA)" <jira@apache.org>
To: dev@jackrabbit.apache.org
Subject: [jira] Resolved: (JCR-610) Upgrade to Derby 10.2
In-Reply-To: <3979171.1162153216456.JavaMail.root@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

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

Jukka Zitting resolved JCR-610.
-------------------------------

    Resolution: Fixed

Upgraded jackrabbit-core to use Derby 10.2.1.6 in revision 485605. Passes all unit tests and seems to work fine with existing repositories, so likely no manual upgrade steps are required.

There are some improvements in the Derby 10.2 disk layout that are by default not enabled when using a database created with 10.1. To get full benefits in 10.2, one needs to include the "upgrade=true" attribute in the JDBC connection string. I'll probably include a note about this in the Jackrabbit 1.2 release notes.

> Upgrade to Derby 10.2
> ---------------------
>
>                 Key: JCR-610
>                 URL: http://issues.apache.org/jira/browse/JCR-610
>             Project: Jackrabbit
>          Issue Type: Improvement
>          Components: core
>            Reporter: Jukka Zitting
>         Assigned To: Jukka Zitting
>             Fix For: 1.2
>
>
> Apache Derby 10.2 was released recently. The release contains a number of improvements (including performance) and requires no special upgrade procedures. I suggest we upgrade to Derby 10.2 along with Lucene 2.0 (JCR-352) and Maven 2 (JCR-332).

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