[
https://issues.apache.org/jira/browse/SLING-9862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17222685#comment-17222685
]
Dan Klco commented on SLING-9862:
---------------------------------
[~enorman] I prefer the declarative nature of a specific bundle header vs
overriding existing functionality within the jcr.contentloader. If we did want
to go the route of the jcr.contentloader, would it make sense to use a
different file type than .txt? I can't say I've ever heard of / loaded a .txt
file via JCR content loader, but I don't think it's intuitive that a .txt file
gets treated as a RepoInit file.
> 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)
