Re: [VOTE] Release Apache Groovy 2.5.3 (take 2)

+1 (binding) All tests ran OK. Tested local 2.5.3 with JaCoCo regarding a pending PR on @Gnenerated support: all good as well. --- Java Champion; Groovy Enthusiast JCP EC Associate Seat http://andresalmiray.com http://www.linkedin.com/in/aalmiray -- What go

Re: [VOTE] Release Apache Groovy 2.5.3 (take 2)

At this point, -1. See below. $ gpg --verify apache-groovy-src-2.5.3.zip.asc gpg: assuming signed data in 'apache-groovy-src-2.5.3.zip' gpg: Signature made Thu 11 Oct 2018 07:34:42 AM CEST gpg:using RSA key 6A65176A0FB1CD0B gpg: Good signature from "Paul King " [unknown] gpg:

Re: [VOTE] Release Apache Groovy 2.5.3 (take 2)

Ah yes, indeed. Consuming Groovy 2.5.3 as a library is OK. Consuming it as a standalone distro is broken like Cedric shows. --- Java Champion; Groovy Enthusiast JCP EC Associate Seat http://andresalmiray.com http://www.linkedin.com/in/aalmiray -- What goes u

Re: [VOTE] Release Apache Groovy 2.5.3 (take 2)

We should add a distribution test as part of the release automation. I wanted to do this but didn't find time... Le ven. 12 oct. 2018 à 10:29, Andres Almiray a écrit : > Ah yes, indeed. Consuming Groovy 2.5.3 as a library is OK. Consuming it as > a standalone distro is broken like Cedric shows.

Re: [VOTE] Release Apache Groovy 2.5.3 (take 2)

It is OK to run `groovy -version` under win10. Cheers, Daniel.Sun - Daniel Sun Apache Groovy committer Blog: http://blog.sunlan.me Twitter: @daniel_sun -- Sent from: http://groovy.329449.n5.nabble.com/Groovy-Dev-f372993.html

Re: [VOTE] Release Apache Groovy 2.5.3 (take 2)

This can be caused by having GROOVY_HOME pointing to a different release, unsetting that environment variable or setting to the 2.5.3 directory should fix it. On Fri, Oct 12, 2018 at 1:05 AM Cédric Champeau wrote: > At this point, -1. See below. > > $ gpg --verify apache-groovy-src-2.5.3.zip.asc

Re: [VOTE] Release Apache Groovy 2.5.3 (take 2)

Yes works for me on 4 OSs so long as GROOVY_HOME isn't hard-coded to some other value. And I observe the same behavior as reported by Cédric with 2.5.2 when GROOVY_HOME is hard-coded. Cheers, Paul. On Fri, Oct 12, 2018 at 10:42 PM John Wagenleitner < john.wagenleit...@gmail.com> wrote: > This ca

Re: [VOTE] Release Apache Groovy 2.5.3 (take 2)

Indeed this works. Changing to +1 then. Le ven. 12 oct. 2018 à 14:50, Paul King a écrit : > Yes works for me on 4 OSs so long as GROOVY_HOME isn't hard-coded to some > other value. > And I observe the same behavior as reported by Cédric with 2.5.2 when > GROOVY_HOME is hard-coded. > > Cheers, Pa

Re: [VOTE] Release Apache Groovy 2.5.3 (take 2)

Aha! Good call. Didn’t change my vote so +1 stands. Sent from my primitive Tricorder > On 12 Oct 2018, at 14:52, Cédric Champeau wrote: > > Indeed this works. Changing to +1 then. > >> Le ven. 12 oct. 2018 à 14:50, Paul King a écrit : >> Yes works for me on 4 OSs so long as GROOVY_HOME isn

Can we get rid of illegal reflective access operation warnings?

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/target/groovy-2.5.3/

Re: High Level DSL for Database Querying

Team, As suggested by Jochen Theodorou in this post, I have created this topic for `Database DSL` The methods given in this thread are some examples. We can either mod

Text / String processing DSL in groovy for String/Text processing (Both Command line usage and script based usage)

As suggested by Jochen Theodorou in this post, I have created this topic for `Text / String processing` I have always felt that groovy platform itself can have rich set of

More Default String Methods

As suggested by Jochen Theodorou in this link post, I have created this topic for `More Default String Methods` I would like to work in these if the community accepts this

Re: Can we get rid of illegal reflective access operation warnings?

> 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