Closed kibotu closed 1 year ago
Usually that means something else, like a resolution strategy, failed (like an npe) and had a large blast radius. You can look as the info log for the errors to see where the problem might be.
good point!
i've attached the log file of
./gradlew --refresh-dependencies --s dependencyUpdates -DoutputFormatter=plain,xml,html --info > build.txt
I can't make sense out of the exceptions exactly though :/
It's trying to find a variant with attribute 'org.gradle.jvm.version' with value '2147483647', but none of the available variants match this. The key is in this line: "The consumer was configured to find attribute 'org.gradle.jvm.version' with value '2147483647'."
We don't use version wildcards though.
By chance do you have empty sub-projects (https://github.com/ben-manes/gradle-versions-plugin/issues/746)?
That is the TARGET_JVM_VERSION_ATTRIBUTE
attribute saying it is compatible with any jvm version (Integer.MAX_VALUE). It was added based on the advice from a Gradle engineer in #727.
Bullseye! That was it, thanks a lot, I've moved my script into a separate job where it is the root gradle project + applying the apply plugin: 'jvm-ecosystem'
and it works now as expected :)
the following dependencies can't be resolved:
note: glide compiler fails, but glide works o.O https://mvnrepository.com/artifact/com.github.bumptech.glide/compiler https://mvnrepository.com/artifact/com.github.bumptech.glide/glide
I can't think of a reason why, e.g. okhttp fails, it's also available on mvncentral https://mvnrepository.com/artifact/com.squareup.okhttp3/okhttp
i'm using the following configuration: