[
https://issues.apache.org/jira/browse/GROOVY-7814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15242070#comment-15242070
]
Paul King edited comment on GROOVY-7814 at 4/22/16 10:06 AM:
-------------------------------------------------------------
Java compilers can accept classes compiled by Groovy with this change but won't
let them be used due to Java's limitation of requiring a specific annotation
value. A typical error:
{noformat}
Main.java:2: error: annotation not valid for an element of type Annotation:
@Deprecated
{noformat}
But the classes can be happily used by Groovy. It would allow a new DSL style
of nested annotations such as some of the examples discussed here:
http://stackoverflow.com/questions/679177/annotation-member-which-holds-other-annotations
was (Author: paulk):
We need to check whether Java compilers would be happy using the compiled class
produced by Groovy with this change
> Consider allowing Groovy to support Arrays of arbitrary annotations as the
> return type of an annotation definition member
> -------------------------------------------------------------------------------------------------------------------------
>
> Key: GROOVY-7814
> URL: https://issues.apache.org/jira/browse/GROOVY-7814
> Project: Groovy
> Issue Type: New Feature
> Reporter: Paul King
> Assignee: Paul King
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
