[jira] [Resolved] (GROOVY-10468) Ability to define system properties for groovyc using CompilerConfiguration

["Paul King (Jira)" <ji...@apache.org>]

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

Paul King resolved GROOVY-10468.
--------------------------------
    Fix Version/s: 3.0.10
                   4.0.1
         Assignee: Paul King
       Resolution: Fixed

> Ability to define system properties for groovyc using CompilerConfiguration
> ---------------------------------------------------------------------------
>
>                 Key: GROOVY-10468
>                 URL: https://issues.apache.org/jira/browse/GROOVY-10468
>             Project: Groovy
>          Issue Type: Documentation
>          Components: Compiler
>    Affects Versions: 3.0.9, 4.0.0
>            Reporter: Marcin Zajaczkowski
>            Assignee: Paul King
>            Priority: Minor
>             Fix For: 3.0.10, 4.0.1
>
>
> In some cases, it would be useful to be able to define system properties for groovyc using CompilerConfiguration.
> The real life example is a limitation of Idea which doesn't allow to provide system properties for groovyc (just for javac) - [https://youtrack.jetbrains.com/issue/IDEA-287642] . As a result, Spock 2.0-groovy-3.0 cannot be easily compiled in Idea if Maven project is imported.
> There are probably also some other situations where CompilerConfiguration might be more handy than playing with Gradle/Maven/Ant/Netbeans configurations.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)