[
https://issues.apache.org/jira/browse/GROOVY-10281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17424111#comment-17424111
]
Eric Milles edited comment on GROOVY-10281 at 10/4/21, 6:55 PM:
----------------------------------------------------------------
Why is it better? Is this something that only benefits developers of Groovy,
not consumers?
Without a clear statement of the benefit(s), I would opt for keeping compiler
configuration as simple as possible.
was (Author: emilles):
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)
