Migrating to refreshVersions breaks the build
See original GitHub issue- I have read the guidelines for submitting issues
🐛 Describe the bug
Migrating my project to refreshVersions breaks the build
💣 Steps to reproduce
- Clone the following branch: https://github.com/marmistrz/OpenMeteo/tree/deps
- Execute
gradle refreshVersionsMigrate
- Execute
gradle build
.
Then the build fails with
* What went wrong:
A problem occurred configuring root project 'OpenMeteo'.
> kotlin.KotlinNullPointerException (no error message)
📱 Tech info
Issue Analytics
- State:
- Created 2 years ago
- Reactions:2
- Comments:6
Top Results From Across the Web
Migrate - gradle refreshVersions
It generates gradle/libs.versions.toml with the current version of all dependencies. It modifies build.gradle(.kts) files, so that dependency notations ...
Read more >Handling versions which change over time
Using dynamic versions in a build bears the risk of potentially breaking it. As soon as a new version of the dependency is...
Read more >Gradle migration - Development - Image.sc Forum
I migrated Apache Calcite build from Maven to Gradle, ... said “it will break everything”; Many said that Maven-based build evolved for very ......
Read more >Hello dear users I am considering adding config options to r ...
... on this draft proposal https github com jmfayard refreshVersions issues 202. ... have it break in a obvious way rather than silently...
Read more >Better dependency management in Android Studio 3.5 with ...
refreshVersions helps Gradle users with the tedious manual work usually ... this error message is the exact moment where it all breaks down....
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
The version
0.22.0
will include the fix, and if you’re in a hurry, the version0.22.0-SNAPSHOT
is being built and should be there in less than 5 minutes.I see this happening on a brand new project with basically nothing in it. This looks like a regression on
0.21.0
. If i drop back to0.20.0
this error doesn’t happen