This message was deleted.

Can you provide your build scripts, or optimally an MCVE showing the problem?

Sorry, no. If I had that, it would probably be very easy. But it only happens in this one big build, and not according to any pattern I recognize. That's why I was hoping someone else might have seen this before.

Without any additional info I'd recommend to look into groovy artifacts in plugins/buildSrc classpaths for version conflicts (esp with gradle provided groovy artifacts) since it seems to happen while evaluating project

@grossws Thanks, that was a good hint! I found this:

|    \--- org.hidetake:groovy-ssh:2.10.1
|         +--- org.codehaus.groovy:groovy-all:2.5.6

Excluding groovy there seemed to help, but since the warnings did not show up every time, I cannot be totally certain, yet.

It may depend on jars order in classpath and if there're hashsets/hashmaps anywhere to build classpath it could be non-deterministic. If you use groovy dsl (`build.gradle`/`settings.gradle` instead of `build.gradle.kts`/`settings.gradle.kts`) all sets/maps are suspect iirc

Yeah, we're using groovy DSL, even for our build-logic plugins (i.e.

foobar.gradle

, not

foobar.groovy

). Might convert to something else at some point, but not soon, probably