[
https://issues.apache.org/jira/browse/SLING-9617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler resolved SLING-9617.
-------------------------------------
Resolution: Fixed
Added in rev
https://github.com/apache/sling-slingfeature-maven-plugin/commit/8acf654eeb9eaff831ddfca5b1787beaab768163
An extension named apis-jar-config can now contain these properties (taking
precedence):
{noformat}
{
"license-report" : "PATH",
"license-header" : "STRING or STRING ARRAY",
"license-footer" : "STRING or STRING ARRAY",
"license-defaults" : ["PATTERN", "PATTERN"],
"javadoc-links" : ["LINK", "LINK"],
"javadoc-classpath-removals" : ["LINK", "LINK"],
"javadoc-classpath-highest-versions" : ["LINK", "LINK"],
"javadoc-classpath-tops" : ["LINK", "LINK"],
"javadoc-source-level" : "STRING",
"api-version" : "STRING",
"bundle-resource-folders" : ["STRING", "STRING"],
"bundle-resources" : ["STRING", "STRING"],
"region-mapping" : {
"REGION" : "MAPPED_NAME"
},
"classifier-mapping" : {
"CLASSIFIER" : "MAPPED_NAME"
},
"manifest-entries" : {
"key" : "value"
}
}
{noformat}
> Allow to specify api generation parameters through feature extension
> --------------------------------------------------------------------
>
> Key: SLING-9617
> URL: https://issues.apache.org/jira/browse/SLING-9617
> Project: Sling
> Issue Type: New Feature
> Components: Maven Plugins and Archetypes
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Priority: Major
> Fix For: slingfeature-maven-plugin 1.3.14
>
>
> For some parameters of the api generation like for example the javadoc
> classpath or the license configuration, it makes sense to have them as part
> of the feature model.
> We should allow some configuration parameters to be provided by a feature
> model extension
--
This message was sent by Atlassian Jira
(v8.3.4#803005)