[
https://issues.apache.org/jira/browse/OAK-10340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17741510#comment-17741510
]
Marcel Reutegger commented on OAK-10340:
----------------------------------------
The pull request also fixes another issue in MutableTree.moveTo(). The call to
the underlying NodeBuilder.moveTo() may returns false. In this case, the
MutableTree must not change state, but it currently does. It incorrectly
changes its parent to the move target already before NodeBuilder.moveTo(). I
added a test that exercises this scenario.
> Child order not updated on source after move
> --------------------------------------------
>
> Key: OAK-10340
> URL: https://issues.apache.org/jira/browse/OAK-10340
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: core
> Reporter: Marcel Reutegger
> Assignee: Marcel Reutegger
> Priority: Minor
>
> The hidden child order property on the source parent of a move operation is
> not updated when the moved node was orderable under the source parent.
> The issue does not seem serious, because AbstractTree.getChildNames() is
> quite lenient and will add children not present in :childOrder at the end of
> the returned Iterable.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
