Gradle shouldn't spam the output with KERBEROS errors when it succeeds

[KotlinIsland]

Related to #17157

Under corporate proxy the output is spammed with hundreds of errors even though the network is working, Gradle should suppress these errors as they are misleading and irrelevant.

NEGOTIATE authentication error: No valid credentials provided (Mechanism level: No valid credentials provided (Mechanism level: Failed to find any Kerberos tgt))
KERBEROS authentication error: No valid credentials provided (Mechanism level: Failed to find any Kerberos tgt)

[ljacomet]

This is most likely the underlying library's output and not from Gradle itself.

This is unlikely to get attention from the Gradle team because of other priorities.
What could help is indicate whether there is a way to configure the underlying library to be quieter.

Any chance you could help with that?

[KotlinIsland]

What library is it? can you point me to a place in the code and I'll take a look.

[ljacomet]

This is most likely org.apache.httpcomponents:httpclient which is at version 4.5.13 in recent Gradle versions.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. Given the limited bandwidth of the team, it will be automatically closed if no further activity occurs. If you're interested in how we try to keep the backlog in a healthy state, please read our blog post on how we refine our backlog. If you feel this is something you could contribute, please have a look at our Contributor Guide. Thank you for your contribution.

[KotlinIsland]

not stale