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 2022/07/19 07:15:00 UTC

[jira] [Resolved] (GROOVY-10691) POJO transform applies to only top-level types

     [ https://issues.apache.org/jira/browse/GROOVY-10691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Paul King resolved GROOVY-10691.
--------------------------------
    Fix Version/s: 5.0.0-alpha-1
                   4.0.4
         Assignee: Paul King
       Resolution: Fixed

Hopefully fixed by:
[https://github.com/apache/groovy/commit/4c9565850115]

 

I think there is still scope for us to better nail down the behavior for nested classes inside an existing POJO without further annotations but at least the explicit annotation case is covered for now.

> POJO transform applies to only top-level types
> ----------------------------------------------
>
>                 Key: GROOVY-10691
>                 URL: https://issues.apache.org/jira/browse/GROOVY-10691
>             Project: Groovy
>          Issue Type: Bug
>          Components: Static compilation
>    Affects Versions: 4.0.3
>            Reporter: Christopher Smith
>            Assignee: Paul King
>            Priority: Minor
>             Fix For: 5.0.0-alpha-1, 4.0.4
>
>
> The logic for the {{@POJO}} annotation is applied only to top-level classes, even if the nested classes are explicitly annotated with {{@CompileStatic}}.
> {code}
> @CompileStatic @POJO
> class MetaClassExcluded {
>   @CompileStatic @POJO
>   static class StillHasMetaClass {}
> }
> {code}
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)