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-2243) Automatic upgrade to 2.0
Date Wed, 20 Jan 2010 13:56:54 GMT

     [ https://issues.apache.org/jira/browse/JCR-2243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Jukka Zitting resolved JCR-2243.

    Resolution: Fixed

I added a backwards compatibility section the the Jackrabbit 2.0 release notes and included
the following:

    Repositories that have used the new JSR 283 security features included
    as a development preview in Jackrabbit 1.5 and 1.6 may face problems
    when upgrading to Jackrabbit 2.0. See especially JCR-1944 and JCR-2313
    for more details.

I guess that's enough for now on this issue, so resolving as fixed.

> Automatic upgrade to 2.0
> ------------------------
>                 Key: JCR-2243
>                 URL: https://issues.apache.org/jira/browse/JCR-2243
>             Project: Jackrabbit Content Repository
>          Issue Type: New Feature
>          Components: jackrabbit-core
>            Reporter: Jukka Zitting
>            Priority: Blocker
>             Fix For: 2.0.0
> Jackrabbit 2.0 contains some changes that are not compatible with repositories created
with earlier versions. It would be nice if Jackrabbit would automatically detect and upgrade
repositories created with 1.x versions.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message