[
https://issues.apache.org/jira/browse/OAK-2990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
angela resolved OAK-2990.
-------------------------
Resolution: Won't Fix
The property {{jcr:lastModified}} is defined by a specific mixin type
{{mix:lastModified}} and must not be set with a different node type (i.e.
changing it's declaring node type and thus ending up with a different
{{PropertyDefinition}}.
Unfortunately the design of the user sync in it's current form does not allow
for setting addition mixin types to the user (which has shown to be a bit
unfortunate when trying to address critical issues). Therefore this improvement
is not possible without a complete redesign of the user sync which I don't
consider to be feasible and justifiable at the moment.
> Make sync fill jcr:lastModified in addition to rep:lastSynced
> -------------------------------------------------------------
>
> Key: OAK-2990
> URL: https://issues.apache.org/jira/browse/OAK-2990
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: auth-external
> Affects Versions: 1.2.2
> Reporter: Nicolas Peltier
> Priority: Minor
>
> while rep:lastSynced is crucial not to re-run sync at every login, having the
> information that the sync didn't change anything (and thus no action should
> be taken for that user) would be very interesting. I guess a jcr:lastModified
> property would do the trick.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
