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

Posted to dev@sling.apache.org by "angela (JIRA)" <ji...@apache.org> on 2017/06/21 08:02:00 UTC

[jira] [Updated] (SLING-6973) Adjust AbstractSlingRepository2 to reflect SLING-6963

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

angela updated SLING-6973:
--------------------------
    Attachment: SLING-6973.patch

original patch as proposed on github. see SLING-6963 for some additional discussion. in particular [~fmeschbe] suggested to use reflection instead... i leave that up to the Sling team to decide. Afaik at Adobe we already use the most recent version of the service-user-mapping anyway.

> Adjust AbstractSlingRepository2 to reflect SLING-6963
> -----------------------------------------------------
>
>                 Key: SLING-6973
>                 URL: https://issues.apache.org/jira/browse/SLING-6973
>             Project: Sling
>          Issue Type: Improvement
>          Components: JCR
>            Reporter: angela
>         Attachments: SLING-6973.patch
>
>
> Splitting off the adjustment of {{AbstractSlingRepository2}} from SLING-6963 in order to make sure the enhancement for the serviceusermapping bundle can be treated separately from the (optional) changes to the {{AbstractSlingRepository2}}.
> IMHO it makes sense to also reflect the enhancement in the _jcr.base_ module to actually illustrated the intention inside the Sling code base.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)