(Issue) Deprecated Gradle features were used in this build, making it incompatible with Gradle 9.0

What is the reason for this problem?

PS E:\Projects\test\........> ./gradlew clean build

Java HotSpot(TM) 64-Bit Server VM warning: Sharing is only supported for boot loader classes because bootstrap classpath has been appended

[Incubating] Problems report is available at: file:///E:/Projects/test/......../build/reports/problems/problems-report.html

Deprecated Gradle features were used in this build, making it incompatible with Gradle 9.0.

You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.

For more on this, please refer to https://docs.gradle.org/8.12.1/userguide/command_line_interface.html#sec:command_line_warnings in the Gradle documentation.

BUILD SUCCESSFUL in 26s

problems-report.html

By the way, @Vampire , if it’s not your job to facilitate communication between the backend and users, or help solve technical issues related to Gradle, then what exactly is your job? Moderating the forum? Because I honestly don’t understand what you’re doing here if it’s not to help the community.

Someone who participates in a technical forum like this has a job. If that job is not to help users solve problems or clarify doubts, then I don’t know what your purpose is. Could you clarify?

My job is to develop software for my employer, which - as I said - is not Gradle Inc.
I’m not affiliated to Gradle in any way.
My job regarding this forum is nothing, I do not have any job related to this forum.
This is mainly a user community where users like me help users like you.
What I do here is spending my spare time, trying to help fellow users.
And being treated like shit for spending my sparse spare time to help others does not really help keep up the motivation. :wink:

And regarding your actual question, as I said in the other thread.
If you run with --warning-mode all the deprecation warnings are accompanied with links to documentation that explains further the problems and possible solutions.
For some reason the incubating problems report you screenshotted does not have these links it seems.

But as even that report says, your first deprecation problem is, that you depend on implicitly added dependencies for your tests that you should add explicitly, the link from the normal deprecation warning will show more information. The second deprecation problem is, that for some reason your test task does not execute any tests which - as said in the other thread - can have many problems and without seeing your project or an MCVE noone else can tell you what the actual underlying reason is, just that you try to execute a test task that does not result in any tests being executed.