[ 
https://issues.apache.org/jira/browse/GROOVY-8226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Paul King updated GROOVY-8226:
------------------------------
    Description: 
This sub-task is about making Groovy aware of the target types TYPE_USE and 
TYPE_PARAMETER for JDK8+.

The Groovy compiler should be able to compile annotation definitions containing 
these targets rather than producing the current error:
{noformat}
BUG! exception in phase 'class generation' in source unit 'ConsoleScript1' 
unsupported Target TYPE_USE
{noformat}

Also, after this change, Groovy should be able to use annotations that have a 
target of TYPE_USE or TYPE_PARAMETER plus one or more other targets. The 
annotation should be usable according to whatever other targets are specified. 
Adapting Groovy to also be able to use the annotation at places corresponding 
to TYPE_USE or TYPE_PARAMETER is the subject of another issue(s).

> JSR308 initial plumbing tweaks
> ------------------------------
>
>                 Key: GROOVY-8226
>                 URL: https://issues.apache.org/jira/browse/GROOVY-8226
>             Project: Groovy
>          Issue Type: Sub-task
>            Reporter: Paul King
>
> This sub-task is about making Groovy aware of the target types TYPE_USE and 
> TYPE_PARAMETER for JDK8+.
> The Groovy compiler should be able to compile annotation definitions 
> containing these targets rather than producing the current error:
> {noformat}
> BUG! exception in phase 'class generation' in source unit 'ConsoleScript1' 
> unsupported Target TYPE_USE
> {noformat}
> Also, after this change, Groovy should be able to use annotations that have a 
> target of TYPE_USE or TYPE_PARAMETER plus one or more other targets. The 
> annotation should be usable according to whatever other targets are 
> specified. Adapting Groovy to also be able to use the annotation at places 
> corresponding to TYPE_USE or TYPE_PARAMETER is the subject of another 
> issue(s).



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to