v0.9.5 no longer automatically loads the latest version, is this wanted?
See original GitHub issueI noticed that, in case a version is unspecified in the version.properties
file, refreshVersions 0.9.5 does not bind it to the latest it can, but fails with a message like:
* What went wrong:
Execution failed for task ':refreshVersions'.
> Couldn't resolve version for ModuleId(group=com.github.kittinunf.fuel, name=fuel-coroutines)
I used this auto-select-latest feature to manually migrate up to date stuff quickly, was it dropped purposefully? It can make it a little harder to migrate, especially when there are unknown custom version key rules, or when they change.
Issue Analytics
- State:
- Created 3 years ago
- Comments:11 (8 by maintainers)
Top Results From Across the Web
Go Modules Reference - The Go Programming Language
Introduction. Modules are how Go manages dependencies. This document is a detailed reference manual for Go's module system. For an introduction to creating ......
Read more >YAP (Yet Another Player) v0.9.5 - Doom9's Forum
YAP (Yet Another Player) v0.9.5 Software players. ... Yap will use them automatically, if DirectShow decide to load it to the graph.
Read more >Release Notes - Chocolatey Software Docs
Chocolatey is software management automation for Windows that wraps installers, executables, zips, and scripts into compiled packages.
Read more >Release Notes | Google Cloud CLI Documentation
Rebuilt gcloud-crc32c 1.0.0 on latest version of golang. Updated gsutil component to ... It is no longer needed by other Google Cloud ML...
Read more >Upgrading - Krill documentation - NLnet Labs
Krill upgrades may sometimes require that existing data is migrated to a new format used by the new release. Krill will perform these...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
We definitely need to have integration test with gradleTestKit() so that we can test this kind of stuff with different versions of Gradle.
Pablisco has quite good gradleTestKit tests in https://github.com/pablisco/auto-module We could steal stuff from him
I found the culprit: it’s in Gradle and appeared when I added support for authenticated repos. I reported that bug and I’ll do what I can to have it fixed in Gradle 6.7 so we can kiss this issue goodbye: https://github.com/gradle/gradle/issues/14694