How can I force update all the snapshot Gradle dependencies in intellij

Intellij IdeaGradleIntellij 14

Intellij Idea Problem Overview


I have a project with SNAPSHOT dependencies using gradle as its build tool in intellij.

The problem is that intellij is using SNAPSHOTS that are now outdated. enter image description here

When I build the project on the command line

gradle build or 
gradle clean build --refresh-dependencies

On command line the latest dependencies are fetched. I also setup my grade file to always download snapshot dependencies according to this answer.

How can I force intellij to download all dependencies?

Intellij Idea Solutions


Solution 1 - Intellij Idea

In IntelliJ 2017.2 you can right-click on the project name in the Gradle Tool Window and select Refresh dependencies from the context menu.

Refresh Gradle dependencies in IntelliJ 2017.2

This will refresh all your dependencies, not only the SNAPSHOTS, so it might take a while. I don't know if other versions of IntelliJ also have this feature.

Solution 2 - Intellij Idea

I have run into some very sticky snapshots. There are a few options you can try:

  • On the Gradle tab (right side of UI), click the blue circling arrows icon, which should refresh the dependencies (works in most cases)
  • If that does not work, try running the gradle command in IntelliJ using the Green "run Gradle command" icon - this runs the command in IntelliJs environment not that of your local machine.
  • If both of those fail, you can modify your Gradle resolutionStrategy settings to something like:
    configurations.all {
        resolutionStrategy.cacheDynamicVersionsFor 4, 'hours'
        resolutionStrategy.cacheChangingModulesFor 4, 'hours'
    }

This config change is a last-ditch option and should be used sparingly. It basically tells Gradle to refresh the local cache more often. You should click the IntelliJ Gradle refresh button after making these changes.

Solution 3 - Intellij Idea

Another option is to open up the Project Structure, and under Project Settings, Libraries, find the dependency in the list and remove it. Then press the Gradle refresh blue circling arrows icon and IntelliJ should fetch the latest version.

enter image description here

enter image description here

Solution 4 - Intellij Idea

IntelliJ IDEA ULTIMATE 2020.1

Right-click on the project name in the Gradle Tool Window and select Refresh Gradle Dependencies from the context menu.

enter image description here

Solution 5 - Intellij Idea

EDIT

On Gradle 6+, snapshots are changing by default. So, no need to set changing = true anymore.


Previous answer:

Gradle caches changing modules for 24 hours by default. We can tell Gradle to refresh or redownload dependencies in the build script by marking those as 'changing'.

Follow these steps:

Step #1: Tell Gradle not to cache changing modules by set the value of the cacheChangingModulesFor property to 0 second:

configurations.all {
    resolutionStrategy.cacheChangingModulesFor 0, 'seconds'
}

Step #2: Mark dependencies which are needed to be refreshed or redownloaded, as changing module:

dependencies {
    implementation("com.howtoprogram.buysell:payment-api:0.0.1-SNAPSHOT") {
        changing = true
    }
}

Source: Refresh or Redownload Dependencies in Gradle

Solution 6 - Intellij Idea

The easiest way to ensure that IntelliJ adds all dependencies is to invalidate the project caches and restart. It will take about a minute to reload the project.

INTELLIJ IDE

File -> Invalidate Caches/Restart...

Now as for ensuring that the latest snapshot is used, you must specify the version of the dependency you are using in your gradle.build file.

Typically there is no 'latest' anchor version in most repositories. You'll simply have to look and see what the latest version is.

Theoretically if you knew the release dates and versioning system you could write a Groovy function that returned the dependency URL and pass it to implementation.

def getLatestVersion(){
 ...build version string
return version //As string
}

implementation getLatestVersion()

But it would not be recommended even if you referencing a CI/CD pipeline in case there were any changes outside of your control

Attributions

All content for this solution is sourced from the original question on Stackoverflow.

The content on this page is licensed under the Attribution-ShareAlike 4.0 International (CC BY-SA 4.0) license.

Content TypeOriginal AuthorOriginal Content on Stackoverflow
QuestionVad1moView Question on Stackoverflow
Solution 1 - Intellij IdeaElliot VargasView Answer on Stackoverflow
Solution 2 - Intellij IdeacjstehnoView Answer on Stackoverflow
Solution 3 - Intellij IdeakuporificView Answer on Stackoverflow
Solution 4 - Intellij IdeaTechPassionateView Answer on Stackoverflow
Solution 5 - Intellij IdeaAnggrayudi HView Answer on Stackoverflow
Solution 6 - Intellij IdeaBrian AndersonView Answer on Stackoverflow