[jira] [Resolved] (GROOVY-10770) Multiple @CompileStatic annotations don't combine extensions

["Eric Milles (Jira)" <ji...@apache.org>]

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

Eric Milles resolved GROOVY-10770.
----------------------------------
    Fix Version/s: 5.0.0-alpha-1
       Resolution: Fixed

https://github.com/apache/groovy/commit/168ac8f269620f3d2bef85dbabd364823f8f2dec

> Multiple @CompileStatic annotations don't combine extensions
> ------------------------------------------------------------
>
>                 Key: GROOVY-10770
>                 URL: https://issues.apache.org/jira/browse/GROOVY-10770
>             Project: Groovy
>          Issue Type: Bug
>          Components: Static Type Checker
>    Affects Versions: 4.0.5
>            Reporter: Christopher Smith
>            Assignee: Eric Milles
>            Priority: Major
>             Fix For: 5.0.0-alpha-1
>
>
> When multiple levels of {{@CompileStatic}} are present, various type-checking extensions can be specified independently, but the total list isn't aggregated:
> {code:groovy}
> @CompileStatic(extensions = 'some-extension.groovy')
> class MyClass {
>   @CompileStatic(extensions = 'erroneously-skipped.groovy')
>   def myMethod() {}
> }
> {code}
> In such a case, all extensions should be applied collectively, inmost first. It might also make sense at some point to add some configuration to undo/disable other extensions, but for now composition is the piece that's not working correctly.
> I speculate that unified handling for {{@CompileStatic}} and {{@TypeChecked}} might be needed to make the various flavors all work together as expected by end users.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)