Re: A reminder about how things are compiled

Yes. 2017-12-27 14:24 GMT+01:00 Jochen Theodorou : > On 27.12.2017 13:59, Cédric Champeau wrote: > >> Actually I just tested with the native IntelliJ import, that is to say >> _without_ calling "gradle idea", and it just works out of the box (but >> there seem to be a weird

Re: A reminder about how things are compiled

On 27.12.2017 13:59, Cédric Champeau wrote: Actually I just tested with the native IntelliJ import, that is to say _without_ calling "gradle idea", and it just works out of the box (but there seem to be a weird delay after the execution of a test). you mean the intellij gradle import?

Re: A reminder about how things are compiled

I think the IDE setup can be improved. I didn't take at shot at this yet. 2017-12-27 13:22 GMT+01:00 Jochen Theodorou : > On 27.12.2017 10:04, Cédric Champeau wrote: > [...] > >> The consequence, however, is that any change to a Java class in Groovy >> core is going to produce

Re: Lack of a wild card in DefaultGroovyMethods

On 27.12.2017 03:11, Nathan Harvey wrote: A few methods in DefaultGroovyMethods don't utilize wildcards, for example, the Map plus operator: public static Map plus(Map left, Map right) { ... } Which causes a compile error on the following, for example: Map

Re: A reminder about how things are compiled

On 27.12.2017 10:04, Cédric Champeau wrote: [...] The consequence, however, is that any change to a Java class in Groovy core is going to produce a different compiler. This is fine in the IDE, as long as I do not have to bootstrap immediately... which I do not have to. But I must say the

A reminder about how things are compiled

Hi fellow Groovy contributors! Given the recent question from Jochen about how to only execute tests from the "core" project when you "know you only modified core" triggering re-execution of tests for all modules, let me explain why this is like this. Groovy is partially written in Groovy. It