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/03/26 17:32:00 UTC

[jira] [Commented] (GROOVY-10001) Generated getMetaClass should incorporate annotations

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

Eric Milles commented on GROOVY-10001:
--------------------------------------

I think is is marked both {{@Generated}} and {{@Internal}}.  Is there a way to configure Dynamo to ignore any method with one of those annotations?

> Generated getMetaClass should incorporate annotations
> -----------------------------------------------------
>
>                 Key: GROOVY-10001
>                 URL: https://issues.apache.org/jira/browse/GROOVY-10001
>             Project: Groovy
>          Issue Type: Improvement
>          Components: Compiler
>    Affects Versions: 3.0.7
>            Reporter: Christopher Smith
>            Priority: Major
>
> I'm trying to work around [an annoying AWS SDK bug|https://github.com/aws/aws-sdk-java-v2/issues/2348] by adding this to my trait:
> {code:groovy}
> @DynamoDbIgnore
> abstract MetaClass getMetaClass()
> {code}
> I had hoped that this would get applied to the generated method, but in fact it didn't. It would be immensely useful for cases like this to be able to somehow apply annotations to the generated {{getMetaClass}} method, either by this hack or perhaps by annotating the class.



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