Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Deprecation warning: Resolution of the configuration :xxx:classpathCopy was attempted from a context different than the project context #729

Closed
tribbloid opened this issue Feb 16, 2023 · 1 comment

Comments

@tribbloid
Copy link

Observed in both version 0.45.0 and 0.44.0, here 0.44.0 was used to avoid triggering:

#727

Can only be visible if "--warning-mode all" is enabled:

$ ./gradlew dependencyUpdates --warning-mode all

...
Resolution of the configuration :xxx:classpathCopy 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 behavior has been deprecated. This will fail with an error in Gradle 9.0. See https://docs.gradle.org/8.0/userguide/viewing_debugging_dependencies.html#sub:resolving-unsafe-configuration-resolution-errors for more details.
...

No stacktrace or pointer to part of the source code was in the error message. I assume this will be improved in Gradle 9.0. But ideally the plugin could be fixed before that

@ben-manes
Copy link
Owner

haha, you opened this in #680 👋

It's been a warning since Gradle 5, but a major change to migrate and not pressing concern for them to break the ecosystem. For now it is to guide new plugins, though PRs are welcome is anyone wants to try reworking ours.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants