You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@groovy.apache.org by "Eric Milles (Jira)" <ji...@apache.org> on 2021/10/12 18:53:00 UTC

[jira] [Updated] (GROOVY-9789) Stubbing: Mode of running Groovyc to only output stubs

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

Eric Milles updated GROOVY-9789:
--------------------------------
    Component/s: Stub generator / Joint compiler

> Stubbing: Mode of running Groovyc to only output stubs
> ------------------------------------------------------
>
>                 Key: GROOVY-9789
>                 URL: https://issues.apache.org/jira/browse/GROOVY-9789
>             Project: Groovy
>          Issue Type: Improvement
>          Components: Compiler, Stub generator / Joint compiler
>            Reporter: Endre Stølsvik
>            Priority: Major
>
> So, I'd love if I could instruct groovyc to only perform the Java stubbing part (and stop there).
> The rationale for this is described in this StackOverflow question: [https://stackoverflow.com/q/53759596/39334]
> Basically, *I want to have three-way joint/mixed compilation between Java, Groovy and Kotlin.* And I figure that if I first could get the java stubs of all groovy files, I could manage to do this in four steps as described in the SO question.
> If this logic holds, it would probably hold for other languages too, so it could conceivably be a nice feature to have not only for my scenario with Java+Groovy+Kotlin.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)