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 2018/10/18 14:31:00 UTC

[jira] [Updated] (SLING-8012) Extract an HTL runtime bundle from the existing HTL modules

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

Radu Cotescu updated SLING-8012:
--------------------------------
    Fix Version/s: Scripting HTL Models Use Provider 1.0.8
                   Scripting HTL JS Use Provider 1.0.28
                   Scripting HTL Engine 1.1.0-1.4.0
                   Scripting HTL Java Compiler 1.1.0-1.4.0
                   Scripting HTL Compiler 1.1.0-1.4.0

> Extract an HTL runtime bundle from the existing HTL modules
> -----------------------------------------------------------
>
>                 Key: SLING-8012
>                 URL: https://issues.apache.org/jira/browse/SLING-8012
>             Project: Sling
>          Issue Type: Improvement
>          Components: Scripting
>            Reporter: Radu Cotescu
>            Assignee: Radu Cotescu
>            Priority: Major
>             Fix For: Scripting HTL Compiler 1.1.0-1.4.0, Scripting HTL Java Compiler 1.1.0-1.4.0, Scripting HTL Engine 1.1.0-1.4.0, Scripting HTL JS Use Provider 1.0.28, Scripting HTL Models Use Provider 1.0.8
>
>
> An HTL runtime bundle would facilitate deployments where all scripts are already precompiled, reducing the number of modules that need to be available on the platform. The compilation phase should become optional and the HTL engine should be able to work without the front-end and back-end compilers.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)