Skip to content
This repository has been archived by the owner on Aug 15, 2024. It is now read-only.

Deprecation warning: "configuration foo was resolved without accessing the project in a safe manner" #143

Open
iamdanfox opened this issue Dec 5, 2019 · 0 comments

Comments

@iamdanfox
Copy link
Contributor

What happened?

The configuration :witchcraft-oauth2:allProcessors was resolved without accessing the project in a safe manner. This may happen when a configuration is resolved from a thread not managed by Gradle or from a different project. See https://docs.gradle.org/5.6.4/userguide/troubleshooting_dependency_resolution.html#sub:configuration_resolution_constraints for more details. This behaviour has been deprecated and is scheduled to be removed in Gradle 6.0.

stacktrace includes:

at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1041)
at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:821)
at groovy.lang.GroovyObjectSupport.invokeMethod(GroovyObjectSupport.java:44)
at org.inferred.gradle.ProcessorsPlugin$_configureIdeaPlugin_closure6$_closure27$_closure28.doCall(ProcessorsPlugin.groovy:165)
at java.lang.reflect.Method.invoke(Method.java:566)
at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:326)

setupIdeaAnnotationProcessing(project, idea.module, it.asNode(), allProcessorConf)

What did you want to happen?

No deprecation warnings I guess!

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

No branches or pull requests

1 participant