Closed johnjohndoe closed 1 month ago
Thanks for your answer. After looking at this issue, I've updated to Kotlin
2.0.20-Beta1
and I no longer have the issue ✅.
https://github.com/ben-manes/gradle-versions-plugin/issues/874#issuecomment-2247068237
With 2.0.20-Beta1
the lower end of the report looks like this:
...
The following dependencies exceed the version found at the milestone revision level:
- org.jetbrains.kotlin:compose-compiler-gradle-plugin [2.0.20-Beta1 <- 2.0.0]
https://kotlinlang.org/
- org.jetbrains.kotlin:kotlin-gradle-plugin [2.0.20-Beta1 <- 2.0.0]
https://kotlinlang.org/
- org.jetbrains.kotlin:kotlin-scripting-compiler-embeddable [2.0.20-Beta1 <- 2.0.0]
https://kotlinlang.org/
The following dependencies have later milestone versions:
- com.github.ligi:tracedroid [3.1 -> 4.1]
Failed to determine the latest version for the following dependencies (use --info for details):
- com.google.testing.platform:android-driver-instrumentation
- com.google.testing.platform:android-test-plugin
- com.google.testing.platform:core
- com.google.testing.platform:launcher
- org.jetbrains.kotlin:kotlin-build-tools-impl
- org.jetbrains.kotlin:kotlin-stdlib
2.0.0
- org.robolectric:android-all
Gradle current updates:
- Gradle: [8.9: UP-TO-DATE]
It looks like the lookup still does not work.
2.0.20-Beta1 is newer than 2.0.0. Technically this is correct, but it should be 2.0.0 -> 2.0.20-Beta1
.
Maven's version plugin displays as (current version)...(suggested version), but doesn't report all scenarios, which seemed useful to do merely for debugging purposes. The formatting is a little weird but keeps it consistent to be less confusing, and the section is mostly a warning of a possible configuration issue that the report would suggest a downgrade based on what its update queries found.
I am not concerned about the kotlin
lines. I like to point out the unresolved dependencies in the Failed to determine the latest version for the following dependencies
block.
you'd have to use --info
to see what the error was
When I run the task on your project, I see it spends a long time on rejections,
Selection of com.android.tools.utp:android-test-plugin-host-apk-installer:31.6.0-alpha06 rejected by component selection rule: Rejected by rejectVersionIf
If I remove that logic and use the beta plugin then it all resolves correctly
Oh! How do you remove com.android.tools.utp:android-test-plugin-host-apk-installer
?
if it doesn't have a stable release then when you're rejecting all non-stable the resolution fails. You could instead use
rejectVersionIf {
isNonStable(it.candidate.version) && !isNonStable(it.currentVersion)
}
I see. In combination with 2.0.20-Beta1
the rejectVersionIf
helps. Seems this will be a temporary issue which disappears with new version of the dependencies... hopefully. Thank you for the workaround.
Project setup
Project link
Report
Related