Jochen is right, Groovy compilation happens after stubgen and javac, hence it'll replace those previously generated classes.
Why shouldn't javac compile the stubs? Wouldn't javac need the classes so that it has something to compile against (since Java is statically compiled) so that circular compilation works? GMaven worked this way also. -Keegan On Nov 21, 2016 4:36 PM, "Jochen Theodorou" <[email protected]> wrote: > On 21.11.2016 23:08, Winnebeck, Jason wrote: > >> I recently encountered an error from javac compiling a stub that was >> otherwise valid from Groovy itself when I enabled generate-stubs task. I >> resolved the error properly, but I wonder, should javac be compiling >> stubs when using gmavenplus? >> > > afaik no > > I thought it just referred to them but did >> not compile them. If it’s compiling the stubs, am I at risk of having >> the stub replace the Groovy-generated code in the final jar? >> > > since groovy compilation happens after the groovy compiler will overwrite > those classes. So no danger from that front > > bye Jochen >
