On Wed, Oct 23, 2024 at 3:50 AM Paul King <pa...@asert.com.au> wrote: > > Definately something we should look at. A few folks we'd need to work with to > make that happen. My thinking is let's get Geb over the line first and then > we can repeat for a few other projects if/as needed.
I'd love to have Geb joining Apache Groovy. One question I've got is this tho: is there enough community left to [at least semi-]actively maintain it? Thanks, Roman. > > On Wed, Oct 23, 2024, 6:57 PM Guillaume Laforge <glafo...@gmail.com> wrote: >> >> It'd be nice (beyond the existing bundling) to further include it as a >> dedicated module. >> Also updated to more modern Java idioms, I guess. >> And maybe it could be the occasion to evolve Groovy to add some constructs >> like async / await like in other languages, but that could be backed by >> GPars. >> >> Guillaume >> >> >> On Wed, Oct 23, 2024 at 10:42 AM Balachandran Sivakumar >> <balachand...@balachandran.org> wrote: >>> >>> Hi All, >>> >>> Just like we are voting to bring in Geb under the Apache Groovy >>> umbrella, can we also do something about GPars[1]? It's a useful project >>> that was run by late Dr. Russel, a Groovy committer IIRC. Thanks >>> >>> [1] https://gpars.org/ >>> >>> -- >>> Thank you, >>> Balachandran Sivakumar >>> >>> >> >> >> -- >> Guillaume Laforge >> Apache Groovy committer >> Developer Advocate @ Google Cloud >> >> Blog: glaforge.dev >> Twitter: @glaforge >> Mastodon: @glafo...@uwyn.net
