You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@sling.apache.org by "Eric Norman (Jira)" <ji...@apache.org> on 2023/05/15 16:14:00 UTC

[jira] [Resolved] (SLING-11874) MockNode should auto-set created/lastModified prop values when appropriate

     [ https://issues.apache.org/jira/browse/SLING-11874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Eric Norman resolved SLING-11874.
---------------------------------
    Resolution: Fixed

Merged PR at:  [{{dbfcc6b}}|https://github.com/apache/sling-org-apache-sling-testing-jcr-mock/commit/dbfcc6bc20a857d5397d0d91de80601c1beee05f]

> MockNode should auto-set created/lastModified prop values when appropriate
> --------------------------------------------------------------------------
>
>                 Key: SLING-11874
>                 URL: https://issues.apache.org/jira/browse/SLING-11874
>             Project: Sling
>          Issue Type: Improvement
>          Components: Testing
>            Reporter: Eric Norman
>            Assignee: Eric Norman
>            Priority: Major
>             Fix For: Testing JCR Mock 1.6.10
>
>
> MockNode should auto-set system generated value if the specified property definition is known to expect it.  This should happen in the addNode and the addMixin methods.
> Specifically the jcr:created, jcr:createdBy, jcr:lastModified and jcr:lastModifiedBy properties should be assign generated values when appropriate.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)