József Bartók

> This feels too early. We shouldn't start nagging when the only replacement is @Incubating. Let's wait until at least 8.4 with this. Yup, have no intention of merging this...

Note to self: revert being too clever in deprecation messages.

> Note to self: revert being too clever in deprecation messages. Done.

@bot-gradle test RFN

@bot-gradle test and merge

Confirmed regression in `8.3`, seems Ivy related: ``` * Exception is: org.gradle.api.tasks.TaskExecutionException: Execution failed for task :getDependencies. at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.lambda$executeIfValid$1(ExecuteActionsTaskExecuter.java:149) at org.gradle.internal.Try$Failure.ifSuccessfulOrElse(Try.java:282) at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeIfValid(ExecuteActionsTaskExecuter.java:147) at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.execute(ExecuteActionsTaskExecuter.java:135) at org.gradle.api.internal.tasks.execution.FinalizePropertiesTaskExecuter.execute(FinalizePropertiesTaskExecuter.java:46) at org.gradle.api.internal.tasks.execution.ResolveTaskExecutionModeExecuter.execute(ResolveTaskExecutionModeExecuter.java:51) at...

Thank you for providing a valid report. The issue is in the backlog of the relevant team and is prioritised by them.

This test (and one other) are brittle in the sense that they fail, if some other test leaves JMX metrics lying around (for example after it had failed for some...

Yes, found the relevant comment in `ClientJmxMetricsTest`. But still, these tests should not fail because something else left garbage around, so I've made sure of that. > // if failing,...

> What are the use-cases for TAPI model polymorphism? Shouldn't TAPI models just represent flat data? One type of use-case is pre-existing models, please see * https://github.com/gradle/gradle/pull/29038 Another use case...