> Hi,
>
> It's long overdue, but the status quo is not really nice. Running Groovy
> on Java 9+ gives warnings like this:
>
> WARNING: An illegal reflective access operation has occurred
> WARNING: Illegal reflective access by
> org.codehaus.groovy.vmplugin.v7.Java7$1
> (file:/tmp/groovy-2.5.3/targ
Understandable but sorry to hear it all the same.
For the record, I make a lot of use of GPars and it is extremely reliable
and solid. I've been on the verge of submitting a pull request to add
back-pressure to the actor classes since that's my main pain point in using
the library.
Thanks for all
On Fri, May 24, 2019 at 10:28 AM Paul King wrote:
> Also, if you have anything you'd particularly like to see in Groovy 4,
> please discuss. I'll have a slide on potential things in Groovy 4 in my
> gr8conf talk next week. I'd like to include as many sensible ideas as
> possible to make use of t
Hi all,
I was looking into various uses of Groovy that require serialization of the
underlying library classes (for example, Spark, etc) and found that one of
the road blocks is that the built in IntRange class isn't serializable.
For example, this test fails:
new File('test.ser').withObject
Chiming in late here, but the only one I would passionately argue about is
the string <=> numeric conversions. The implicit conversions to / from
String already in Groovy have been responsible for a large proportion of
the impactful bugs that have come out of my complex groovy code. For
example, th
Hi all,
I noticed after updating to Groovy 3.0 that some of my groovy applications
were misbehaving when I ran them inside a GNU screen session, but not
outside. I investigated a bit more and saw that when running on Linux,
startGroovy overrides the TERM variable and hard codes it to "linux" no
ma
but spam was becoming a
> problem when self-serve accounts were being used.
>
> See also some guidelines for creating PRs if you want to work on the fix:
>
> https://groovy.apache.org/#code
>
> Cheers, Paul.
>
>
>
> On Sat, Feb 18, 2023 at 10:32 AM Simon Sadedin w
Hi all,
I sent this to groovy-users but didn't get much response. I am trying to
understand some behaviour that is causing subtle and odd bugs in our code,
which might be a bug or might be something I don't understand.
The behaviour is that under very specific circumstances, Groovy is coercing
a
Sorry all - sent without a subject, so resending to correct that.
I sent this to groovy-users but didn't get much response. I am trying to
> understand some behaviour that is causing subtle and odd bugs in our code,
> which might be a bug or might be something I don't understand.
>
> The behaviour
much appreciated!
I looked through the documentation pretty thoroughly and couldn't see an
answer there so it would be good to have something people can find if they
encounter it in a confusing way.
Cheers,
Simon
10 matches
Mail list logo
