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 05:59:00 UTC

[jira] [Comment Edited] (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:comment-tabpanel&focusedCommentId=17568338#comment-17568338 ] 

Paul King edited comment on GROOVY-10691 at 7/19/22 5:58 AM:
-------------------------------------------------------------

Right, so it doesn't seem to have a metaclass but it still has all the inner class mop methods.


was (Author: paulk):
Right, so it doesn't seem to have a metaclass but it still has all the mop methods.

> 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
>            Priority: Minor
>
> 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)