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

Konrad Windszus resolved SLING-10297.
-------------------------------------
    Resolution: Fixed

Fixed in 
https://github.com/apache/sling-org-apache-sling-jcr-contentloader/commit/372e212078ee0a5da31f21943d9a5d6ec96a509b.

> Expose org.apache.sling.jcr.contentloader.internal.PathEntry as API
> -------------------------------------------------------------------
>
>                 Key: SLING-10297
>                 URL: https://issues.apache.org/jira/browse/SLING-10297
>             Project: Sling
>          Issue Type: Improvement
>    Affects Versions: JCR ContentLoader 2.4.0
>            Reporter: Konrad Windszus
>            Assignee: Konrad Windszus
>            Priority: Major
>             Fix For: JCR ContentLoader 2.4.2
>
>          Time Spent: 2h 10m
>  Remaining Estimate: 0h
>
> To ease parsing the {{Sling-Initial-Content}} header outside the OSGi 
> container context (e.g. for SLING-10243) it would be useful to expose the 
> {{PathEntry}} 
> (https://github.com/apache/sling-org-apache-sling-jcr-contentloader/blob/235a16eaa8cb6ed0fde56b1966e6506d1edae46f/src/main/java/org/apache/sling/jcr/contentloader/internal/PathEntry.java)
>  as API



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to