Hi Alexander,
this is the mailing list about development of the Groovy language, not
develpers using Groovy, so maybe the us...@groovy.apache.org would be
more appropriate.
I am no expert on this, but have you tried using the non-indy version of
Groovy 2.5.x and does the bug also occur there (I saw
groovy-2.5.6-indy.jar in the stack trace you posted) ?
(Both versions have basically the same performance characteristics, but
non-indy is much more widely used, and therefore much better tested.)
Cheers,
mg
On 03/05/2021 15:32, Alexander Veit wrote:
Hi,
please give me a hint if this is the inappropriate mailing list for
this question.
