[MAGNOLIA-5386] Create a NodeType migration task that removes 'childNodeDefinition' referencing metaData NodeType. Created: 14/Oct/13  Updated: 22/Oct/13  Resolved: 18/Oct/13

Status: Closed
Project: Magnolia
Component/s: core
Affects Version/s: 5.1
Fix Version/s: 5.1.1

Type: Task Priority: Neutral
Reporter: Eric Hechinger Assignee: Eric Hechinger
Resolution: Fixed Votes: 0
Labels: 4.5_to_5_migration
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to MAGNOLIA-5365 Create a NodeType migration task Closed
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Date of First Response:

 Description   

Create a NodeType migration task that remove for all registered NodeType the 'childNodeDefinition' reference to metaData.

http://wiki.magnolia-cms.com/pages/viewpage.action?pageId=73666272



 Comments   
Comment by Daniel Lipp [ 15/Oct/13 ]

RemoveMetaDataInNodeTypeDefinitionTask

  • pls remove #97 - #101 (no added value)

RemoveMetaDataInNodeTypeDefinitionTaskTest

  • I'd either go for no javadoc or just "Tests." - the more you right the more likely there's a mistake
  • line #90 - 95 should be like
            // 4.5.x do not have a 'mgnl:created' definition
            try {
                nodeTypeManager.getNodeType(NodeTypes.Created.NAME);
                fail("nodeTypeManager should throw a NoSuchNodeTypeException as 4.5 NodeTypeDefinition do not define a 'mgnl:created'");
            } catch (NoSuchNodeTypeException ne) {
            }
    
    
Comment by Tobias Mattsson [ 17/Oct/13 ]

The javadoc on RemoveMetaDataInNodeTypeDefinitionTask#getNodeTypesToRegister is incorrect, it should say that it returns node type definitions where the metadata child node definition has been removed.

Generated at Mon Feb 12 04:04:40 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.