You are viewing a plain text version of this content. The canonical link for it is here.

Posted to oak-issues@jackrabbit.apache.org by "Tomek Rękawek (JIRA)" <ji...@apache.org> on 2016/02/23 13:18:18 UTC

[jira] [Updated] (OAK-3910) Migrating node inheriting from mix:versionable without version history

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

Tomek Rękawek updated OAK-3910:
-------------------------------
    Attachment: OAK-3910.patch

> 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
>            Priority: Minor
>         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
(v6.3.4#6332)