[
https://issues.apache.org/jira/browse/SLING-10463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17359392#comment-17359392
]
Angela Schreiber commented on SLING-10463:
------------------------------------------
[~rma61...@adobe.com], yes..... they are tedious to troubleshoot. but figuring
out what happened once odd bugs/regression pop up if nobody even noticed that
there was a same-named-node-property issues might be next to impossible. so,
i'd rather go for failing as early and loudly as possible. also, i don't
remember having seen a same-named-node-property collision with repo-init in the
all the years.... so maybe it's really an edge case. wdyt?
> Repoinit fails to create node if property already exists at the same path
> -------------------------------------------------------------------------
>
> Key: SLING-10463
> URL: https://issues.apache.org/jira/browse/SLING-10463
> Project: Sling
> Issue Type: Bug
> Components: Repoinit
> Reporter: Tom Blackford
> Priority: Minor
> Attachments: SLING-10463.patch
>
>
> If a property already exists at the path of a node described in repoinit,
> then the repoinit will incorrectly assume the node does not need to be
> created.
> Test case & fix - [^SLING-10463.patch]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
