Deprecation warnings with Gradle 7

[Chessray]

Running dependencyUpdates with Gradle 7.0.2 produces a lot of warnings like this one:

Resolution of the configuration <some task> was attempted from a context different than the project context. Have a look at the documentation to understand why this is a problem and how it can be resolved. This behaviour has been deprecated and is scheduled to be removed in Gradle 8.0. See https://docs.gradle.org/7.0.2/userguide/viewing_debugging_dependencies.html#sub:resolving-unsafe-configuration-resolution-errors for more details.

[ben-manes]

See #263, #335. The Gradle team has to provide assistance if they want to break compatibility for a 9yr old plugin or force it’s depreciation. Alternatively, they can incorporate the features directly as we proposed from the beginning. This requires an invasive rewrite which is beyond my free time and a big ask for a contributor. Instead of helping us the Gradle team delayed the changes and don’t incorporate this plugin’s features because it’s been free labor. It’s not sustainable that way.

[Chessray]

Linking this to Gradle Github