#31990

The lock in the queue is highly contentious and may block project
configuration for a prolonged period of time. In gradle/gradle build,
the time spent locked goes up to 500ms per project, because their
configuration is effectively serialized.

This commit doesn't address the root cause, but highlights the
time-consuming operation in the build traces.

This isn't needed right now.

We've introduced another level of nesting.

We use an exception annotated with @contextual so that the error appears in the console.

This brings up a bigger question whether this annotation is worth having or not, or if we should
just print all exceptions to the console. I can see there being many exceptions that are being hidden
because of this annotation and the logic behind it

…#32154)

Signed-off-by: Christoph Obexer <[email protected]>

nagging whenever the flag is set, even if the value matches the default.
The flag is planned for removal in 9.0

The computation of the loadAfterStore parameter is made lazy, so that the DeprecationLogger has enough time to configure the problem reporting. Otherwise, the deprecation nagging is ignored silently.
The order of the computation is also changed, so that the nagging is unconditional, rather than being dependent on the short-circuiting of boolean expressions.

for readability

…ped dependencies block (#32048)