[
https://issues.apache.org/jira/browse/SLING-9862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17223030#comment-17223030
]
Eric Norman commented on SLING-9862:
------------------------------------
[~jsedding] Ok, I understand where you are coming from. It's just that your
proposed solution looked nearly identical to the jcr.contentloader solution so
it seemed like it would be a candidate for reusing the existing code. I'm
still not sure we need yet another way to load/initialize the repository which
seems like it may confuse the users regarding what is the "right" way to do
such things.
> 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)
