jackrabbit-oak-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael Dürig (JIRA) <j...@apache.org>
Subject [jira] [Commented] (OAK-157) Incorrect rebase/edit/merge logic
Date Fri, 29 Jun 2012 07:24:42 GMT

    [ https://issues.apache.org/jira/browse/OAK-157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13403748#comment-13403748

Michael Dürig commented on OAK-157:

Some things broke with then changes made for OAK-153. See [respective comment|https://issues.apache.org/jira/browse/OAK-153?focusedCommentId=13403747&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13403747].

> Incorrect rebase/edit/merge logic
> ---------------------------------
>                 Key: OAK-157
>                 URL: https://issues.apache.org/jira/browse/OAK-157
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: core
>            Reporter: Jukka Zitting
> When working on OAK-154 and adding our first commit hook that modifies the incoming commit
we encountered some problems with the way the KernelNodeStoreBranch class handles the somewhat
tricky rebase/edit/merge case.
> The most pressing issue is that the merge() call ends up in an infinite loop whenever
the configured CommitEditor returns anything that's not equal to the "after" argument it was

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message