[
https://issues.apache.org/jira/browse/SLING-6639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15926709#comment-15926709
]
Karl Pauls commented on SLING-6639:
-----------------------------------
I guess we pretty much have to.
Obviously, it is an incompatible change but granted, as it wasn't intended to
be this way in the first place, it might be possible that nobody else really
used that package so from a versioning perspective one could argue it isn't a
big deal. However, the problem is that in an update of the bundle if the bundle
is still started it would probably rewire to the old version and be broken
until a refresh occurs if the version doesn't get bumped to 2.0.0.
Unless it is a big problem I would just bump the version to 2.0.0 and be done
with it.
> 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)
