[
https://issues.apache.org/jira/browse/CALCITE-2196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16379726#comment-16379726
]
jingzhang commented on CALCITE-2196:
------------------------------------
[~julianhyde], we need to set two system properties before starting jvm:
1. org.codehaus.janino.source_debugging.enable , set to true
2. org.codehaus.janino.source_debugging.dir, set to a path
After code was generated, mark the path in step2 as generated sources root or
sources root or directly set the output path to the existed sources root at
step 2. Then we could step into the generated code
> Update codeGen of metadataHandler in JaninoRelMetadataProvider to include
> Class definition at begin of dynamic code.
> --------------------------------------------------------------------------------------------------------------------
>
> Key: CALCITE-2196
> URL: https://issues.apache.org/jira/browse/CALCITE-2196
> Project: Calcite
> Issue Type: Bug
> Components: core
> Reporter: jingzhang
> Assignee: Julian Hyde
> Priority: Trivial
>
> JaninoRelMetadataProvider uses IClassBodyEvaluator to compile generated code.
> The generated classes can not be debugged in interactively using Idea using
> the method referenced by http://janino-compiler.github.io/janino/ because
> generated code only contains classBody.
> If using ISimpleCompiler to compile complete compile unit instead of
> classBody, we could step into the code.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
