This message was deleted.

The specific error is printed out (clipped off the top of your screenshot).

I know, people not familiar with Gradle are misled systematically

not that misleading - the specific build failure error is always there.

And in this specific case, it looks like the deprecation notice can easily be removed: version catalogs are enabled by default in Gradle 7.4.2, so you can safely remove the corresponding

enableFeature

from the settings script: https://scans.gradle.com/s/x26lxaznv5gro

I think the UX issue is that

Publishing build scan

doesn't really catch the attention like "See and share this link to find out what's wrong"

The much more fatal thing is, that for each and every build failure people are sent to here or the forums and then ask questions absolutely irrelevant regarding the topic Gradle, because every failed build says that you get help here. 😞

Yes, another good reason to nudge people to open the build scan URL instead of the warning for plugin authors 🙂

Users don't really need to open the build scan url, they just need to read one line above and see "ah, it is a compile error because I wrote my code wrongly"

My use case: I have front-end typescript colleagues who use my Kotlin server on their laptop and ping me if there is a build error. The build scan error is 100% of what I need to help them

Yes, for you as the build maintainer the build scan is gold of course. I meant for the build runner or the one with zero Gradle experience just copying a build script from StackOverflow.

Another issue is that Android Studio is pretty dumb when a build error occurs, and it shows the deprecation warning and hide the real stuff

Yeah, that hopefully gets improved with https://youtrack.jetbrains.com/issue/IDEA-226613, please up-vote it

I agree that this output should be better. When you scroll up from

BUILD FAILED

you have to cross irrelevant information before getting to the real error. Could you file an issue about that to get a conversation started? I wonder if moving the deprecation information after

BUILD FAILED

could help, or making sure we print what went wrong after instead of before it. (and indeed remove the generic reference to the help.gradle.org 😛 or make it less visible)