You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@groovy.apache.org by Paul King <pa...@asert.com.au> on 2026/05/12 10:58:49 UTC
Update on GROOVY-12005
Another thing which happened recently is that some of our CI builds started
failing. This appears to be due to some changes to a Cloudflare layer in
front of maven central that impacted Ivy dependency resolution that caused
fragility in downloading grapes. GrapeIvy now has some resiliency built in
to try to combat that fragility and an opt-out mechanism if the extra
checks now in place aren't needed in some environments. I haven't seen any
official notice of changes to maven central, so please shout if you know
more or believe these extra checks were just a temporary phase and aren't
needed permanently.
Cheers, Paul.
Re: Update on GROOVY-12005
Posted by Paul King <pa...@asert.com.au>.
And P.S., I'm still keen on folks testing out the Maven Resolver grape
mechanism which AFAIK isn't impacted by the recent changes.
Cheers,
Paul.
On Tue, May 12, 2026 at 8:58 PM Paul King <pa...@asert.com.au> wrote:
>
> Another thing which happened recently is that some of our CI builds
> started failing. This appears to be due to some changes to a Cloudflare
> layer in front of maven central that impacted Ivy dependency resolution
> that caused fragility in downloading grapes. GrapeIvy now has some
> resiliency built in to try to combat that fragility and an opt-out
> mechanism if the extra checks now in place aren't needed in some
> environments. I haven't seen any official notice of changes to maven
> central, so please shout if you know more or believe these extra checks
> were just a temporary phase and aren't needed permanently.
>
> Cheers, Paul.
>
>