drill-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From paul-rogers <...@git.apache.org>
Subject [GitHub] drill pull request #716: DRILL-5116: Enable generated code debugging in each...
Date Sat, 07 Jan 2017 06:30:16 GMT
Github user paul-rogers commented on a diff in the pull request:

    https://github.com/apache/drill/pull/716#discussion_r95053577
  
    --- Diff: exec/java-exec/src/main/resources/drill-module.conf ---
    @@ -167,10 +167,12 @@ drill.exec: {
         debug: true,
         janino_maxsize: 262144,
         cache_max_size: 1000,
    -    // Enable to write generated source to disk. See ClassBuilder
    -    save_source: false,
         // Where to save the generated source. See ClassBuilder
         code_dir: "/tmp/drill/codegen"
    --- End diff --
    
    Using Eclipse, the /tmp/drill/codegen directory is very simple: Eclipse prompts for the
source location on the first run, remembers it thereafter, and MacOS cleans up any left-over
generated files on the next restart.
    
    Looks like things are a bit more difficult in IntelliJ. I'll play around a bit to see
if I can find a solution that works well for both tools. I'll create a separate JIRA and PR
for that work.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

Mime
View raw message