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 2017/03/15 16:58:41 UTC

[jira] [Commented] (SLING-6639) Avoid split packages in the HTL Engine and HTL Java Compiler bundles

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

Radu Cotescu commented on SLING-6639:
-------------------------------------

Pushed a potential fix in [r1787079|https://svn.apache.org/r1787079]. [~fmeschbe], [~karlpauls], do we actually have to bump the version from {{bundles/scripting/sightly/java-compiler/src/main/java/org/apache/sling/scripting/sightly/package-info.java}} to 2.0.0?

> Avoid split packages in the HTL Engine and HTL Java Compiler bundles
> --------------------------------------------------------------------
>
>                 Key: SLING-6639
>                 URL: https://issues.apache.org/jira/browse/SLING-6639
>             Project: Sling
>          Issue Type: Task
>          Components: Scripting
>            Reporter: Tomek Rękawek
>            Assignee: Radu Cotescu
>             Fix For: Scripting HTL Engine 1.0.34, Scripting HTL Java Compiler 1.0.10
>
>         Attachments: SLING-6639.patch
>
>
> {{ResourceResolution}} and {{SightlyException}} classes should be moved to the java-compiler bundle, as this is the one exporting {{org.apache.sling.scripting.sightly}} package. Right now they are the part of the engine bundle, which doesn't export anything and it may lead to issues if some bundle tries to use these two classes.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)