[
https://issues.apache.org/jira/browse/SLING-11003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17459907#comment-17459907
]
Carsten Ziegeler commented on SLING-11003:
------------------------------------------
Added to cpconverter in
https://github.com/apache/sling-org-apache-sling-feature-cpconverter/commit/8b7dd81932403987d274d6480df1e701e00c6a99
> Provide option to store bundle symbolic name and version in metadata
> --------------------------------------------------------------------
>
> Key: SLING-11003
> URL: https://issues.apache.org/jira/browse/SLING-11003
> Project: Sling
> Issue Type: Improvement
> Components: Content-Package to Feature Model Converter, Feature
> Model, Maven Plugins and Archetypes
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Priority: Major
> Fix For: Content-Package to Feature Model Converter 1.1.12,
> slingfeature-maven-plugin 1.6.0, Feature Model API Regions Extension 1.4.4
>
>
> The api regions launcher extension is reading each bundle on startup to get
> the symbolic name and version; other tooling is doing this in different
> places as well.
> We could provide an option to the maven plugin and the content package
> converter to store that information in the metadata of the feature model.
> Tooling like the launcher extension can then first check metadata and if not
> present, continue to read the file
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
