Re: [Feedback wanted] GROOVY-11871: Support Maven Resolver based version of Grapes

I have made Groovy 6 use Ivy with Maven as an option. We can swap for Groovy 7.

I have been playing with the service loader concept - it mostly works
with just one or two tests fail. I'll explore that a little more and
back out if the issues can't be resolved.

Re next releases. We have a number of pending PRs which would make
sense for 6.0.0-alpha-1 (async/wait, maven grapes). I'll hold off
until we decide on those before doing that release. I am on hols for a
few days. I'll look at a new 4 and 5 release when I return. I was
going to see whether Carl's release checking script would be suitable
for 5. Groovy 3 requires some work on our release scripts as part of
the maven central changes some time back.

On Sat, Mar 14, 2026 at 12:19 AM Milles, Eric (TR Technology) via dev
<dev-GSC0n/0aZo1d/SJB6HiN2Ni2O/[email protected]> wrote:
>
> I recommend making the new resolver available in Groovy 6 with a target of making it the default in Groovy 7 if Ivy goes archive status or Maven impl proves superior.  The 2.6 rele4ase getting cancelled and not having a release where new parser was available but not on by default was a big miss IMO.
>
> As far as enabling the new resolver, system property or @GrabConfig (just an idea) seem fine to me.  I don't think you need to go the service loader route just yet until you get some more feedback.
>
> I don't see any issue with using the RC5 maven resolver since, as you stated, Groovy 6 itself is alpha or pre-alpha state.
>
>
> Re Ivy: are there any specific bugs that are causing a problem for Grab/Grapes?  I could work on a fix for anything that is a bug not a new feature.
>
>
> P.S. I would like to see a Groovy 5 (and possibly 4 and 3) release in the month of March.