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] Resolved: (JCR-610) Upgrade to Derby 10.2
Date Mon, 11 Dec 2006 11:56:25 GMT
     [ http://issues.apache.org/jira/browse/JCR-610?page=all ]

Jukka Zitting resolved JCR-610.

    Resolution: Fixed

Upgraded jackrabbit-core to use Derby 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


View raw message