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 2020/03/06 17:45:00 UTC

[jira] [Updated] (SLING-9183) The Scripting Bundle Maven Plugin should add the Script Engine short name for each resource type capability

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

Radu Cotescu updated SLING-9183:
--------------------------------
    Component/s:     (was: Scripting)
                 Tooling

> The Scripting Bundle Maven Plugin should add the Script Engine short name for each resource type capability
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: SLING-9183
>                 URL: https://issues.apache.org/jira/browse/SLING-9183
>             Project: Sling
>          Issue Type: Bug
>          Components: Tooling
>            Reporter: Radu Cotescu
>            Assignee: Radu Cotescu
>            Priority: Major
>             Fix For: Scripting Bundle Tracker 0.2.0
>
>
> The Scripting Bundle Tracker cannot determine which Script Engine to use for executing a {{org.apache.sling.scripting.bundle.tracker.internal.PrecompiledScript}}. Since the bundles wired to the tracker provide capabilities to inform about the available resource types, these capabilities should also provide the required Script Engine name for each resource type as an attribute of the {{sling.resourceType}} capability.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)