[ https://issues.apache.org/jira/browse/SLING-10349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17339186#comment-17339186 ]
Eric Norman commented on SLING-10349: ------------------------------------- [~-achim] I tried to reproduce this problem by integrating what you described into the latest starter but I didn't see the same result as you. Both the "yyy" namespace and the "yyy:Foobar" nodetype appeared to be created after starting up. Are there any more details of your distribution that you can share, or perhaps a test project that demonstrates the problem? > Repoinit: Nodetype definitions not working > ------------------------------------------- > > Key: SLING-10349 > URL: https://issues.apache.org/jira/browse/SLING-10349 > Project: Sling > Issue Type: Bug > Components: Repoinit > Reporter: Achim Koch > Assignee: Bertrand Delacretaz > Priority: Minor > > Tried to register nodetypes and namespaces like so: > register namespace ( yyy ) http://yyy.com/jcr/nt/1.0 > register nodetypes > <<=== > << <yyy='http://yyy.com/jcr/nt/1.0'> > << [yyy:Foobar] > nt:unstructured > ===>> > The whole repoinit script was ignored, then. (I created a "marker" with > createuser that also was not executed). > I saw no apparent error in the logfile. > The namespace did register, when I removed the whole "register nodetypes" > block. > Btw. the documentation could be more explicit that (if) "<< > <yyy='http://yyy.com/jcr/nt/1.0'>" already creates a namespace (or if that is > required to reference an existing one in the scope of the CND block) -- This message was sent by Atlassian Jira (v8.3.4#803005)