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/09 21:09:00 UTC

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

    [ https://issues.apache.org/jira/browse/SLING-9183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17055316#comment-17055316 ] 

Radu Cotescu edited comment on SLING-9183 at 3/9/20, 9:08 PM:
--------------------------------------------------------------

Fixed in [commit 109b633|https://github.com/apache/sling-scriptingbundle-maven-plugin/commit/109b633] and [commit 7c69a2b|https://github.com/apache/sling-org-apache-sling-scripting-bundle-tracker-it/commit/7c69a2b].


was (Author: radu.cotescu):
Fixed in [commit 109b633|git@github.com:apache/sling-scriptingbundle-maven-plugin/commit/109b633].

> The Scripting Bundle Maven Plugin should add the Script Engine short name for each provided 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 Maven Plugin 0.2.0
>
>
> The Scripting Bundle Maven Plugin should add the Script Engine short name for each provided resource type capability. This should be done based on the extension of each script in the Maven project. By default, the plugin should provide its default mapping, but the mapping should be configurable, in case multiple script engines can handle the same extensions.



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