You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Jukka Zitting (JIRA)" <ji...@apache.org> on 2014/02/04 19:36:10 UTC

[jira] [Commented] (OAK-533) Define behaviour for and implement mix:lastModified

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

Jukka Zitting commented on OAK-533:
-----------------------------------

It's currently a bit difficult to pass the userid needed for {{jcr:lastModifiedBy}} to the commit hook. Doing this would be much easier with OAK-1387, so postponing further work until that.

> Define behaviour for and implement mix:lastModified
> ---------------------------------------------------
>
>                 Key: OAK-533
>                 URL: https://issues.apache.org/jira/browse/OAK-533
>             Project: Jackrabbit Oak
>          Issue Type: New Feature
>          Components: jcr
>            Reporter: Michael Dürig
>            Assignee: Jukka Zitting
>             Fix For: 0.16
>
>         Attachments: 0001-OAK-533-Define-behaviour-for-and-implement-mix-lastM.patch
>
>
> There has been quite some discussion how to best implement {{mix:lastModified}} for Jackrabbit 2:
> https://issues.apache.org/jira/browse/JCR-2116
> https://issues.apache.org/jira/browse/JCR-2233
> http://markmail.org/thread/ygaktajwdz4z4r5m
> I think we should try to do it right from the start in Oak. 



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)