[jira] [Resolved] (SLING-5172) Provide support for custom sections in the provisioning model

["Carsten Ziegeler (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SLING-5172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Carsten Ziegeler resolved SLING-5172.
-------------------------------------
    Resolution: Fixed

Each section which is unknown to the provisioning model is now added to the additional section property of a feature. When models are merged, all additional sections are aggregated on the merged model

> 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)