[
https://issues.apache.org/jira/browse/SLING-6390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15744702#comment-15744702
]
Konrad Windszus commented on SLING-6390:
----------------------------------------
At least the Engine configuration is useful during development and it is handy
to have a UI for the configuration here to quickly toggle some flags. Please
keep at least that metatype info.
> Remove metatype info for some HTL OSGi configurations
> -----------------------------------------------------
>
> Key: SLING-6390
> URL: https://issues.apache.org/jira/browse/SLING-6390
> Project: Sling
> Issue Type: Improvement
> Components: Scripting
> Reporter: Radu Cotescu
> Assignee: Radu Cotescu
> Fix For: Scripting HTL JS Use Provider 1.0.18, Scripting HTL
> Engine 1.0.28, Scripting HTL Models Use Provider 1.0.6
>
>
> The following components should be modified so that they don't provide any
> configuration metatype information any more, eliminating the complexity of
> having too many configurations in the System Console:
> {noformat}
> org.apache.sling.scripting.sightly.impl.engine.SightlyEngineConfiguration
> org.apache.sling.scripting.sightly.impl.engine.extension.use.JavaUseProvider
> org.apache.sling.scripting.sightly.impl.engine.extension.use.RenderUnitProvider
> org.apache.sling.scripting.sightly.impl.engine.extension.use.ResourceUseProvider
> org.apache.sling.scripting.sightly.impl.engine.extension.use.ScriptUseProvider
> org.apache.sling.scripting.sightly.js.impl.JsUseProvider
> org.apache.sling.scripting.sightly.models.impl.SlingModelsUseProvider
> {noformat}
> Advanced users will still have the possibility to configure the components by
> using {{sling:OsgiConfig}} nodes, however they provide reasonable and tested
> default values.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
