[
https://issues.apache.org/jira/browse/SLING-4952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14697227#comment-14697227
]
Radu Cotescu commented on SLING-4952:
-------------------------------------
This can already be done by providing the following configuration:
{noformat}
org.apache.sling.scripting.sightly.impl.engine.SightlyEngineConfiguration
org.apache.sling.scripting.sightly.devmode=B"true"
{noformat}
> Provide option to dump Java code from Sightly Compiler
> ------------------------------------------------------
>
> Key: SLING-4952
> URL: https://issues.apache.org/jira/browse/SLING-4952
> Project: Sling
> Issue Type: Improvement
> Affects Versions: Scripting Sightly Engine 1.0.2
> Reporter: Konrad Windszus
>
> Currently only the compiled servlets are given out through the
> {{org.apache.sling.commons.fsclassloader}}. The Java sources should be given
> out in addition similar what the
> {{org.apache.sling.scripting.jsp.JspScriptEngineFactory}} does via
> {{jasper.keepgenerated}}. Could you add an option to persist the Java sources
> somewhere. That would ease debugging a lot!
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
