[
https://issues.apache.org/jira/browse/SLING-9187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler updated SLING-9187:
------------------------------------
Fix Version/s: (was: slingfeature-maven-plugin 1.1.20)
Slingstart Maven Plugin 1.9.10
> Allow to provide provisioning model name and runmodes via feature model
> folders
> -------------------------------------------------------------------------------
>
> Key: SLING-9187
> URL: https://issues.apache.org/jira/browse/SLING-9187
> Project: Sling
> Issue Type: Improvement
> Components: Feature Model, Maven Plugins and Archetypes
> Affects Versions: slingfeature-maven-plugin 1.1.18
> Reporter: Karl Pauls
> Assignee: Karl Pauls
> Priority: Major
> Fix For: Slingstart Maven Plugin 1.9.10
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> With SLING-9179 and SLING-9178 we allowed to provide runmodes with the
> feature model folders and a default provisioning model name, respectively.
> I think it would be good to allow a provisioning model name per folder
> similar to what we allow for the runmodes. That would mean we would allow
> more than one attribute per folder - hence, I think we should switch away
> from the delimter "|" we used for the runmodes and just reuse the attributed
> header style we use in OSGi.
> In other words, it would look like:
> <folder>;provisioning.model.name="foo";provisioning.runmodes="author,publish"
>
> I will provide a PR for this - please merge the PR and resolve this issue if
> you like it.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
