You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Radu Cotescu (JIRA)" <ji...@apache.org> on 2016/12/15 13:23:58 UTC
[jira] [Resolved] (SLING-6390) Remove metatype info for some HTL
OSGi configurations
[ https://issues.apache.org/jira/browse/SLING-6390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Radu Cotescu resolved SLING-6390.
---------------------------------
Resolution: Fixed
Fixed in [r1774436|https://svn.apache.org/r1774436].
> 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)