sling-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Karl Pauls (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SLING-6639) Avoid split packages in the HTL Engine and HTL Java Compiler bundles
Date Fri, 17 Mar 2017 16:30:43 GMT

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

Karl Pauls commented on SLING-6639:
-----------------------------------

The good thing about this change too is that previously, we had a cycle between these two
components which is now gone. 

> 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)

Mime
View raw message