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 "Marcel Reutegger (JIRA)" <ji...@apache.org> on 2016/03/07 09:15:40 UTC
[jira] [Resolved] (OAK-4085) Malformed node type definition when
reregistered after upgrade
[ https://issues.apache.org/jira/browse/OAK-4085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marcel Reutegger resolved OAK-4085.
-----------------------------------
Resolution: Fixed
Fix Version/s: (was: 1.4.1)
1.5.0
Simplified the fix based on Angela's comments and added an upgrade test to oak-jcr with a TarMK repository created with Oak 1.0.
Fixed in trunk: http://svn.apache.org/r1733875
> Malformed node type definition when reregistered after upgrade
> ---------------------------------------------------------------
>
> Key: OAK-4085
> URL: https://issues.apache.org/jira/browse/OAK-4085
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: core, jcr
> Affects Versions: 1.3.10
> Reporter: Marcel Reutegger
> Assignee: Marcel Reutegger
> Priority: Blocker
> Fix For: 1.5.0
>
> Attachments: OAK-4085.patch
>
>
> When a node type is reregistered after an upgrade from an earlier release, the resulting node type definition may be malformed. As noted in OAK-3584, the node type representation in content was not compliant with JCR already before. As explained here the situation after an upgrade is even worse: http://markmail.org/message/7kjkqlt3erbocpin
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)