[
https://issues.apache.org/jira/browse/SLING-9862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17240759#comment-17240759
]
Oliver Lietz commented on SLING-9862:
-------------------------------------
For Sling on Karaf I have switched to [external repoinit
statements|https://github.com/apache/sling-org-apache-sling-karaf-configs/commit/a0d41eb84d4d32f88dcf2edfcdbbebf67055030a]
*again* in preparation of using the OSGi R7 JSON configuration format
(leveraging the classpath protocol handler and not the OSGi Configurator, see
SLING-9944).
> Support installing repoinit files listed in bundle header
> ---------------------------------------------------------
>
> Key: SLING-9862
> URL: https://issues.apache.org/jira/browse/SLING-9862
> Project: Sling
> Issue Type: New Feature
> Components: Repoinit
> Affects Versions: Repoinit JCR 1.1.26
> Reporter: Julian Sedding
> Assignee: Julian Sedding
> Priority: Minor
>
> Implement support for a {{Sling-RepoInit}} bundle header that consists of a
> comma separated list of relative paths pointing to resources within the
> bundle. For each bundle with a non-empty {{Sling-RepoInit}} header, a
> {{SlingRepositoryInitializer}} that applies all repoinit files referenced in
> the header, should be dynamically registered.
> Such a mechanism would allow bundles to install their own service-user and
> corresponding ACLs.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
