You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@groovy.apache.org by "Paul King (Jira)" <ji...@apache.org> on 2020/05/14 01:52:00 UTC
[jira] [Resolved] (GROOVY-9534) Groovy could provide an AST
transform to hook into platform logging (JEP 264)
[ https://issues.apache.org/jira/browse/GROOVY-9534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Paul King resolved GROOVY-9534.
-------------------------------
Fix Version/s: 4.0.0-alpha-1
Assignee: Paul King
Resolution: Fixed
Proposed PR merged.
> Groovy could provide an AST transform to hook into platform logging (JEP 264)
> -----------------------------------------------------------------------------
>
> Key: GROOVY-9534
> URL: https://issues.apache.org/jira/browse/GROOVY-9534
> Project: Groovy
> Issue Type: New Feature
> Reporter: Paul King
> Assignee: Paul King
> Priority: Major
> Fix For: 4.0.0-alpha-1
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> We could consider providing an AST transform to simplify making use of platform logging. See "JEP 264: Platform Logging API and Service" for more details[1]. I am unsure whether folks would be used to calling log.log and would prefer the info, warn, debug, etc methods.
> [1][https://openjdk.java.net/jeps/264]
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)