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 2018/10/04 07:28:00 UTC

[jira] [Comment Edited] (GROOVY-8822) Conflict between @Generated and @Delegate

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

Paul King edited comment on GROOVY-8822 at 10/4/18 7:27 AM:
------------------------------------------------------------

Do you have some sample code? I presume the Delegate is a Groovy class but I wonder why nothing like that exists in an existing test case. It should be straight forward enough to check before adding that annotation but I'd like to make sure I understand your scenario fully.


was (Author: paulk):
Do you have some sample code?

> Conflict between @Generated and @Delegate
> -----------------------------------------
>
>                 Key: GROOVY-8822
>                 URL: https://issues.apache.org/jira/browse/GROOVY-8822
>             Project: Groovy
>          Issue Type: Bug
>    Affects Versions: 2.5.3
>            Reporter: François Guillot
>            Priority: Major
>
> I get 
> java.lang.annotation.AnnotationFormatError: Duplicate annotation for class: interface groovy.transform.Generated: @groovy.transform.Generated()
> On a class with a field declared with @Delegate
>  
> Removing @Delegate works around the problem



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)