Run the “Reload all Gradle projects” action (via ctrl/ cmd + shift + A), or click the refresh arrows in the Gradle tool window The action to do it have a different name depending on the IDE:
The file versions.properties is part of the Gradle build.Ĭonsequently, after you have edited it, you need to ensure the IDE gets the changes. Running the refreshVersions task will bring them back (plus any newer available update). If you want to delete these comments, it’s possible too, and it’s safe.
They also allow you to glance at how behind the dependencies are, which is a way to estimate the technical debt of the project regarding the dependencies upgrades. They will not affect your build, and will serve as a reminder to revisit upgrading these dependencies later.
Gradle versions update#
If you decide to not update for now, you can leave the comments there. If you decide to update, just replace the previous version with the update: However, the decision of whether to upgrade or not, when, and towards which version, is best decided by the developers responsible like you. Looking for available updates is certainly a job best done by a computer program (instead of you doing the monkey job of googling, clicking and scrolling for every single used dependency). Apply the updates you want to ¶Īfter you have run the refreshVersions task, you will see the available updates as comments: Gradle refreshVersions is fast: it usually takes less than 10 seconds to execute on relatively big projects. IntelliJ has a handy action named “Execute Gradle Task”:
Hint: You don’t need to leave the IDE to run a Gradle task.
0 kommentar(er)
