[
https://issues.apache.org/jira/browse/SLING-5414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15105105#comment-15105105
]
Bertrand Delacretaz commented on SLING-5414:
--------------------------------------------
I've tried an approach where the slingstart maven plugin generates a bundle
with a "modelfragment" classifier, used by a provisioning model provider bundle
to supply the model at runtime. It works but creates a "chicken and egg"
dependency on the modelfragment bundle in launchpad/builder.
I have saved that variant at
https://github.com/bdelacretaz/sling/tree/SLING-5414-wontwork but will need to
change the strategy in the slingstart plugin - having that optionally inject
the modelfragment bundle in the provisioning model, without having a dependency
on it, should work.
> Make the contents of the provisioning model available at runtime
> ----------------------------------------------------------------
>
> Key: SLING-5414
> URL: https://issues.apache.org/jira/browse/SLING-5414
> Project: Sling
> Issue Type: New Feature
> Components: Maven Plugins and Archetypes
> Affects Versions: Slingstart Maven Plugin 1.4.0
> Reporter: Bertrand Delacretaz
> Assignee: Bertrand Delacretaz
> Priority: Minor
> Fix For: Slingstart Maven Plugin 1.4.2
>
> Attachments: SLING-5414.patch
>
>
> For SLING-5355 we need to make additional sections from the provisioning
> model available at runtime, so that ACLs can be set at startup, and also to
> be able to reuse their definitions later for auditing/verification purposes.
> A simple way to do that is to copy those sections in the sling_bootstrap.txt
> file. I have created a patch that does that, will attach it here for review.
> _edit: as discussed below, we'll make the full text of the model available at
> runtime_
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
