You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@groovy.apache.org by "Eric Milles (Jira)" <ji...@apache.org> on 2021/10/04 18:54:00 UTC

[jira] [Commented] (GROOVY-10281) Add compiler option for logging class generation

    [ https://issues.apache.org/jira/browse/GROOVY-10281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17424111#comment-17424111 ] 

Eric Milles commented on GROOVY-10281:
--------------------------------------

Why is it better?  Is this something that only benefits developers of Groovy only, not consumers?

Without a clear statement of the benefit(s), I would opt for keeping compiler configuration as simple as possible.

> Add compiler option for logging class generation
> ------------------------------------------------
>
>                 Key: GROOVY-10281
>                 URL: https://issues.apache.org/jira/browse/GROOVY-10281
>             Project: Groovy
>          Issue Type: Improvement
>            Reporter: Daniel Sun
>            Priority: Major
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Groovy can log class generation via setting the following JVM options:
> {{groovy.log.classgen}}
> {{groovy.log.classgen.stacktrace.max.depth}}
> But the two options are global for JVM, it's better to provide corresponding options in the compiler configuration scope.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)