[
https://issues.apache.org/jira/browse/GROOVY-11614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Milles updated GROOVY-11614:
---------------------------------
Description:
This is a difference in Java vs Groovy behaviour. Enums must be fully qualified
in Groovy while Java requires them to not be fully qualified.
-This was supposedly fixed, but does not seem to work in 4.0.24. Not sure where
it broke.-
Example:
{code:groovy}
void test(Thread.State ts) {
switch (ts) {
case Thread.State.NEW: // cannot remove "Thread.State."
break
}
}
{code}
was:
This is a difference in Java vs Groovy behaviour. Enums must be fully qualified
in Groovy while Java requires them to not be fully qualified
This was supposedly fixed, but does not seem to work in 4.0.24. Not sure where
it broke
> Enums in switch/case statements that are not fully qualified will cause a
> groovy compile error but Java requires enums to "not" be fully qualified
> --------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: GROOVY-11614
> URL: https://issues.apache.org/jira/browse/GROOVY-11614
> Project: Groovy
> Issue Type: Bug
> Components: Compiler, Static compilation
> Affects Versions: 4.0.24
> Reporter: Saravanan
> Priority: Minor
>
> This is a difference in Java vs Groovy behaviour. Enums must be fully
> qualified in Groovy while Java requires them to not be fully qualified.
> -This was supposedly fixed, but does not seem to work in 4.0.24. Not sure
> where it broke.-
> Example:
> {code:groovy}
> void test(Thread.State ts) {
> switch (ts) {
> case Thread.State.NEW: // cannot remove "Thread.State."
> break
> }
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
