Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Warning in Multi-Module project with gradle 5.6

See original GitHub issue

I am getting this with gradle 5.6.1 on a multi-module project

The configuration :myproject:mymodule:testCompileCopy 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/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.

I see no issues in functionality. Just thought of reporting the warning so that it can be addressed before Gradle 6.0 release.

Issue Analytics

State:
Created 4 years ago
Comments:6 (2 by maintainers)

Top GitHub Comments

4reactions

ben-manescommented, Nov 12, 2020

This is also discussed in #263 opened by the Gradle team, but their proposed solution requires a major overhaul of the plugin. It is a big ask to have us rewrite this, because none of us contributing are experts at Gradle. We have all worked on this plugin ad hoc as a weekend project, someday hoping Gradle would incorporate the feature themselves long term. I am not surprised a best practice from Gradle 1.0 is no longer desired, but we have been supporting the community for 8 years as best effort, for a feature that we originally asked for inclusion with a prototype script posted to the forums. While I can help in bursts, this is large enough of an effort that I am not comfortable commiting towards due to my other responsibilities.

Sorry for spamming the Gradle team and please direct this to whomever owns the affected area these days. @lacasseio @big-guy @ldaley @bigdaz @oehme @ljacomet @melix

0reactions

bric3commented, Nov 13, 2020

Yes I totatlly understand that, I wanted to report the latest developement, i.e. the This behaviour has been deprecated and is scheduled to be removed in Gradle 7.0 warning. As a matter of fact I added a comment in this ticket https://github.com/gradle/gradle/issues/13498#issuecomment-726067425 This is not on their roadmap, but maybe Gradle specialists can help this project.

Top Results From Across the Web

java - gradle cpd plugin cpdCheck warning in multi module ...

I have multi module gradle library project; no application module. I replicated this scenario by creating gradle init library project.

Getting rid of warning in a Spring Boot project being migrated ...

Coding example for the question Getting rid of warning in a Spring Boot project being migrated to the Gradle Kotlin DSL-Springboot.

Improve the Performance of Gradle Builds

To execute project tasks in parallel by default, add the following setting to ... Warning: Gradle's Groovy DSL relies heavily on Groovy's dynamic...

'plugins cannot be applied to '(groovy.lang.Closure)' - YouTrack

IDEA-282704 build.gradle warnings in multi module project - 'plugins' cannot be applied to '(groovy.lang.Closure)' ... I'm using the gradle wrapper 5.6.1:

Gradle Multi-Project Builds for Maven Users - OctoPerf

However, be warned that my experience with Gradle is limited to this ... From Maven Multi-module Project to Gradle Multi-project Build.