[
https://issues.apache.org/jira/browse/GROOVY-8225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17472695#comment-17472695
]
Paul King commented on GROOVY-8225:
-----------------------------------
Yes, we should probably close this. I believe everything we want for now is in
Groovy 4 (including support for Bean Validation 2). There are more cases to
cover, like type annotations embedded in certain code scenarios but we can have
separate issues for those as the need arises.
> Groovy support for JSR 308/JEP 104 (Annotations in more places)
> ---------------------------------------------------------------
>
> Key: GROOVY-8225
> URL: https://issues.apache.org/jira/browse/GROOVY-8225
> Project: Groovy
> Issue Type: New Feature
> Reporter: Paul King
> Priority: Major
>
> Now that master is on JDK 8, we should look at supporting annotations in more
> places (i.e. JSR 308 or some subset thereof).
> It will require some plugin tweaking for configuring annotation nodes and
> also some grammar changes. For the backport in
> particular, we'll need to decide whether we don't backport the relevant
> grammar changes or allow them in the grammar
> but gracefully handle them with appropriate error messages. My initial gut
> feel is we should allow them in the grammar but
> we can make that call after further investigation.
> Some other decisions that might arise.
> * Do we support just a subset of the JSR?
> * Currently we allow the type placeholder '{{def}}' to be elided if an
> annotation takes its place. Does this convention need to change with the
> additional annotation positions or do we need to clarify what happens in
> different scenarios?
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
