Hi Jochen,
1. we build using IntelliJ, and this has occurred independent of the
IntelliJ version for years.
1. (It is now that I work more from home that this becomes more of
a nuiscance, due to much slower upload speed to the server.)
2. Does "Groovyc compiles what you give it to compile" hold true in
this case ?
1. Closures are compiled to classes, but they do not exist as such
in the code, so how would IntelliJ tell Groovyc to compile (or
not compile) the closures in a Groovy source file... ?
2. Based on this I always assumed it is Groovyc who decides to
recreate all those auto-generated closure classes... (?)
Cheers,
mg
On 14/01/2024 14:04, Jochen Theodorou wrote:
On 12.01.24 18:50, MG wrote:
Hi guys,
is there a way to get Groovy not to nedlessly recreate closure class
files during a build which would otherwise just change one or two
non-closure class files ?
The recreation of large numbers of closure class files seems to be
triggered randomly at certain points, and having to continuously
rsync-upload these files to the server after small code changes becomes
a factor in turnaround time...
I think we need a bit more detail. Groovyc compiles what you give it to
compile. If something is deciding one time to compile a set A and
sometimes a set B, then it is because the part controlling Groovyc
decided to do that.
so what is controlling Groovyc in your case? Gradle, Maven, Intellij..?
bye Jochen
