jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tomek Rękawek (JIRA) <j...@apache.org>
Subject [jira] [Commented] (OAK-3910) Migrating node inheriting from mix:versionable without version history
Date Fri, 18 Mar 2016 15:00:38 GMT

    [ https://issues.apache.org/jira/browse/OAK-3910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15201586#comment-15201586

Tomek Rękawek commented on OAK-3910:

There's a failing unit test, investigating right now...

> Migrating node inheriting from mix:versionable without version history
> ----------------------------------------------------------------------
>                 Key: OAK-3910
>                 URL: https://issues.apache.org/jira/browse/OAK-3910
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: upgrade
>            Reporter: Tomek Rękawek
>            Assignee: Julian Sedding
>            Priority: Minor
>             Fix For: 1.6, 1.4.1
>         Attachments: OAK-3910.patch
> The OAK-3844 fixes the way in which the oak-upgrade migrates the {{mix:versionable}}
nodes without version history, by displaying a warning and removing the mixin.
> There's a related case, in which the node without the version history isn't explicitly
declared as {{mix:versionable}}, but the {{jcr:primaryType}} or one of the mixins inherits
from the {{mix:versionable}}. In this case we can't simply remove the mixin. We should display
a warning and create an empty version history.

This message was sent by Atlassian JIRA

View raw message