Hi Jochen,
1. that sounds like a good idea, but I am just wondering if ppl who are
in this situation might not potentially have other (Java) libraries
in use, for which they would need to do the renaming of the class
references also.
2. So maybe having a chapter in the Groovy documentation which explains
how to do this so it plays well with Groovy might be the more
generally applicable & easier to do option ?
1. (Note: "plays well with Groovy" might not be an issue here, but
I am just thinking back to the pains of Minecraft obfuscation
not working with Groovy generated bytecode)
Cheers,
mg
On 20/12/2024 17:52, Jochen Theodorou wrote:
On 20.12.24 14:24, Paul King wrote:
Well, that would be the idea. Maybe not recommended, but currently you
can still use the 4.0.x groovy-servlet jar with Groovy 5. At least for
Groovy servlets with a simple Jetty server test I just tried.
You certainly wouldn't want both the 4 and 5 groovy-servlet jars in
your classpath/modulepath and perhaps there might be reasons later to
not allow mixing those versions.
there was already the suggestion to basically offer both and just use
bytecode transformation (renaming class references). If groovy-servlet
is the only place impacted by this it looks like an option to me. Wdyt?
bye Jochen
