You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Jukka Zitting (JIRA)" <ji...@apache.org> on 2009/08/06 12:38:15 UTC

[jira] Created: (JCR-2243) Automatic upgrade to 2.0

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
            Assignee: Jukka Zitting
             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.


[jira] Updated: (JCR-2243) Automatic upgrade to 2.0

Posted by "Jukka Zitting (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/JCR-2243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jukka Zitting updated JCR-2243:
-------------------------------

    Fix Version/s:     (was: 2.0-beta6)
                   2.0.0

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


[jira] Resolved: (JCR-2243) Automatic upgrade to 2.0

Posted by "Jukka Zitting (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/JCR-2243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jukka Zitting resolved JCR-2243.
--------------------------------

       Resolution: Fixed
    Fix Version/s:     (was: 2.0.0)
                   2.0-beta6

I updated the Jackrabbit compatibility test harness and it reports no more failures when opening Jackrabbit 1.x repositories with Jackrabbit 2.0. Thus 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-beta6
>
>
> 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.


[jira] Resolved: (JCR-2243) Automatic upgrade to 2.0

Posted by "Jukka Zitting (JIRA)" <ji...@apache.org>.
     [ 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.


[jira] Updated: (JCR-2243) Automatic upgrade to 2.0

Posted by "Jukka Zitting (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/JCR-2243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jukka Zitting updated JCR-2243:
-------------------------------

    Priority: Blocker  (was: Major)

Another Jackrabbit 2.0 blocker.

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


[jira] Updated: (JCR-2243) Automatic upgrade to 2.0

Posted by "Jukka Zitting (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/JCR-2243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jukka Zitting updated JCR-2243:
-------------------------------

    Assignee:     (was: Jukka Zitting)

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


[jira] Reopened: (JCR-2243) Automatic upgrade to 2.0

Posted by "angela (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/JCR-2243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

angela reopened JCR-2243:
-------------------------


reopening.... from what i remember we have backwards compatibility issues introduced by

JCR-1944: the property type of privileges has changed from STRING to NAME between 1.5 and 1.6.
                     so upgrading from 1.5 is prone to be problematic.
JCR-2313: the issue lists a couple of areas that could cause problems.

I'm not sure if there is anything we have to do about those. but I would feel comfortable if
we could test these and - if they really turn out to be problems - at least state it somewhere.

thanks



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