Guys,
sorry for brevity, in a hurry now.
If you are considering a real support, note please that the name-based
detection of generated classes won't work without parsing the source due to the
darned packages: unless you parse the source, you can't know in which target
sub-folder the generated
I have created https://issues.apache.org/jira/browse/GROOVY-11291 for
this topic
@OZ: Please feel free to add your angle to the ticket G-)
Cheers,
mg
On 18/01/2024 23:18, MG wrote:
Hi Jochen,
1. For our case we would not need to have obsolete class files to be
deleted, just that no
Hi Jochen,
1. For our case we would not need to have obsolete class files to be
deleted, just that no (typically closure) class files be generated
with a different name, even though they are identical to existing ones.
1. IntelliJ also does not (at least reliably) remove unused classes
Am 15.01.24 um 20:24 schrieb o...@ocs.cz:
Jochen,
On 15. 1. 2024, at 10:35, Jochen Theodorou wrote:
If the goal is to give Groovyc a source file and let it compile that,
but write only certain files... well that is something that could be
worked out.
Well I don't know.
Theoretically, it
Jochen,
> On 15. 1. 2024, at 10:35, Jochen Theodorou wrote:
> If the goal is to give Groovyc a source file and let it compile that,
> but write only certain files... well that is something that could be
> worked out.
Well I don't know.
Theoretically, it would be nice if the compiler wrote only
If the goal is to give Groovyc a source file and let it compile that,
but write only certain files... well that is something that could be
worked out. This is not really incremental compilation like we may know
it from eclipse-java though.
bye Jochen
On 14.01.24 21:43, OCsite wrote:
MG,
I
MG,
I might be wrong (haven't checked for a long long time and at least a couple of
major Groovy versions), but I believe groovyc always simply re-creates all the
.class files which result from a source compiled (could be a number of them:
aside of the closure classes, groovyc — very
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
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
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
10 matches
Mail list logo
