[
https://issues.apache.org/jira/browse/OAK-2287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14358325#comment-14358325
]
Alex Parvulescu commented on OAK-2287:
--------------------------------------
from where I'm standing the patch is good enough. The only remaining question
is if it makes sense to refactor it to be used for any date value that might
conflict in a similar way (ie. custom:lastModified). I can take care of this if
it is interesting to have.
> ConflictHandler for merging jcr:lastModified
> --------------------------------------------
>
> Key: OAK-2287
> URL: https://issues.apache.org/jira/browse/OAK-2287
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: core, jcr
> Reporter: Alex Parvulescu
> Assignee: Alex Parvulescu
> Priority: Minor
> Fix For: 1.2
>
> Attachments: OAK-2287-2.patch, OAK-2287.patch
>
>
> As discussed on oak-dev, 'jcr:lastModified' is a date property and it
> represents the last modification date. It makes sense to merge concurrent
> updates by picking the newer date of the 2 options.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
