ben-manes
commented
5 years ago Are you on the latest version of the plugin? I think we fixed that.
Open kdabir opened 5 years ago
ben-manes
commented
5 years ago Are you on the latest version of the plugin? I think we fixed that.
kdabir
commented
5 years ago yeah, I hope its the latest
id "com.github.ben-manes.versions" version "0.24.0"
bric3
commented
5 years ago I can confirm the issue:
> Task :dependencyUpdates
The configuration :sub-a:annotationProcessorCopy 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.3/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.
The configuration :sub-a:annotationProcessorCopy2 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.3/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.
The configuration :sub-a:apiElementsCopy 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.3/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.
The configuration :sub-a:archivesCopy 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.3/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.
The configuration :sub-a:compileCopy 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.3/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.
The configuration :sub-a:compileCopy2 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.3/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.
...The plugin is only declared in the root project, each subproject only declares its dependency block.
plugins {
id 'com.github.ben-manes.versions' version '0.27.0'
}
ext {
javaProjects = subprojects - project(":doc")
}
allprojects {
group = 'com.company'
}
configure(javaProjects) {
apply plugin: 'java'
apply plugin: 'maven-publish'
repositories {
mavenLocal()
maven {
url 'http://nexus.blbl.cr/nexus/content/groups/public'
}
}
dependencies {
// ...
}
// ...
}
Java 11.0.3 (AdoptOpenJDK 11.0.3+7) Gradle 5.6.3 Versions : 0.27.0
bric3
commented
4 years ago Little update on this one, now gradle warns it will not work any more in gradle 7.0
--stacktraceben-manes
commented
4 years ago 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
bric3
commented
4 years ago 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.
I am getting this with gradle 5.6.1 on a multi-module project
I see no issues in functionality. Just thought of reporting the warning so that it can be addressed before Gradle 6.0 release.