You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2015/10/26 10:40:27 UTC
[jira] [Closed] (SLING-5172) Provide support for custom sections in
the provisioning model
[ https://issues.apache.org/jira/browse/SLING-5172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carsten Ziegeler closed SLING-5172.
-----------------------------------
> Provide support for custom sections in the provisioning model
> -------------------------------------------------------------
>
> Key: SLING-5172
> URL: https://issues.apache.org/jira/browse/SLING-5172
> Project: Sling
> Issue Type: New Feature
> Components: Tooling
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Fix For: Sling Provisioning Model 1.4.0
>
>
> Right now, the provisioning model supports a fixed set of sections - which is fine for the use case at hand.
> However, we often have the need to add additional information for additional tooling. For example, the recent discussion about introducing support for subsystems needs information about exported packages/services in the case of a composite subsystem.
> Launchpad needs things like the web.xml.
> You might want to add additional information like fixed isses, a copyright, license etc.
> Therefore we should support the notion of custom sections and simply add them as text blobs to the feature
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)