[
https://issues.apache.org/jira/browse/SLING-5731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15931615#comment-15931615
]
Oliver Lietz commented on SLING-5731:
-------------------------------------
{quote}
Naturally other components in the system don't work properly if we try to
provide another export of Rhino. In particular some Sightly components break if
they don't get the Rhino engine that is properly configured for them.
{quote} (http://www.mail-archive.com/dev@sling.apache.org/msg58190.html)
[~rr...@adobe.com], can you elaborate on what you tried and what break?
> Export the org.mozilla.javascript.tools package in
> org.apache.sling.scripting.javascript bundle
> -----------------------------------------------------------------------------------------------
>
> Key: SLING-5731
> URL: https://issues.apache.org/jira/browse/SLING-5731
> Project: Sling
> Issue Type: Bug
> Components: Scripting
> Reporter: Tan Huynh
> Attachments: sling-javascript.diff
>
>
> We would like to use the [handlebars template engine
> |https://github.com/jknack/handlebars.java] in our Sling application. This
> bundle has a dependency on the [Rhino Javascript engine
> |https://developer.mozilla.org/en-US/docs/Mozilla/Projects/Rhino].
> The two packages that the Handlebars bundle imports from the Rhino bundle are
> * org.mozilla.javascript
> * org.mozilla.javascript.tools.
>
> The Sling javascript bundle already exports the first package, it would be
> great if it also exports the second package so that we won't have to deploy
> the Rhino javascript bundle to be able to use handlebars.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
