[
https://issues.apache.org/jira/browse/SLING-6763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15964082#comment-15964082
]
Bertrand Delacretaz commented on SLING-6763:
--------------------------------------------
I have committed your contribution, thank you very much!
And also created a sibling org.apache.sling.fragment.nashorn fragment bundle
which means you don't need to edit sling.properties anymore, just install that
bundle to export the Nashorn API package.
However at revision 1790948 the minimal example from the README does not work
for me, it outputs
{code}
<h1>${currentNode.properties.title}</h1>Here's some example text
{code}
Without interpreting the {{currentNode.properties.title}} variable.
What I did is:
* Start a Sling trunk launchpad from scratch
* Install the org.apache.sling.fragment.nashorn fragment and esx bundles,
verify that esx is active
* Run the minimal example from the README
The ESX engine is activated, it's just the interpretation of the readme test
example variable that does not happen.
> Remove org.apache.sling.commons.json dependency from esx engine
> ---------------------------------------------------------------
>
> Key: SLING-6763
> URL: https://issues.apache.org/jira/browse/SLING-6763
> Project: Sling
> Issue Type: Bug
> Components: Scripting
> Reporter: Senol Tas
> Assignee: Bertrand Delacretaz
> Fix For: Scripting ESX 0.2.0
>
>
> remove org.apache.sling.commons.json dependency from esx engine and replace
> with native build in nashorn JSON parser
> + minor updates in the demo package to showcase the usage of dynamically
> changing handlebars templates based on selector.
> + added experimental es6 transpiler as preperation for sandboxing the engine
> + updated demo with es6 classes and imports
> i created a pull request on github:
> https://github.com/apache/sling/pull/209
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
