This message was deleted.

Maybe I'm ignorant, but how is disabling a perfectly valid warning a solution to any problem? It is a "close your eyes and hope for the best" work-around, not a solution imho.

True, but I think we should be allowed to opt in to that if desired.

I don’t think so. I am afraid the issue 16779 was caused by weird usage of

kotlin-dsl

plugin in the build script logic, and the warning is appropriate.

Is it a valid warning? I ask, because I can't do anything to fix or resolve it, and whatever the issue is, it doesn't seem to cause any problems. So the warning message is just noise to me. In my opinion warnings should be actionable. But what action can I take to remedy the problem?

Report it to the plugin misbehaving. In the linked ticket it was the Kotlin Gradle Plugin that had a dependency on kotlin stdlib in a different version than shipped with Gradle instead of using the stdlib that is shipped with Gradle. That plugin was fixed according to JetBrains. If the warning still comes, you probably have other plugins with the same problem. If you for example use a plugin that registers a task with missing input / output annotations in Gradle 6, you also get a warning you can not directly do anything against besides updating to a newer version of the plugin that fixes the problem or report if you are already on the latest version. Same situation here. You use something that is not compatible and need to use a version that is compatible or report upstream to fix the incompatibility.

How can I tell which plugin is misbehaving?

Well, you as user need to direct it to the plugin developer. If they test their plugin and ignore the warning, it was directed at them and they ignored it, so you as user need to tell them to fix their stuff. If they didn't thest their plugin, there is no way to direct the message at them. If they just tested with older Gradle versions or newer Gradle versions where the problem does not arise as versions match, their test matrix is too small, or they just didn't check other version and either need to be told by their users what compatibility they need, or they should explicitly declare with which Gradle versions their plugin is compatible.

Well, you as user need to direct it to the plugin developer.

But I don't know which plugin is causing the problem, or how to find it out 🤷‍♀️ . The warning message doesn't given any indication that it's because of any specific plugin. I'm now more convinced that

WARNING: Unsupported Kotlin plugin version

is unactionable, useless noise that should either be removed, made useful, or changed so I can opt-out of it. It's not even documented. The first link that comes up when I google it is a hacky workaround that doesn't resolve the issue.