Whenever Eclipse starts, it happens very very often (but not always!) that the STS-Gradle integration refreshes the dependencies for at least some of the ~20 projects I have in the workspace.
This is time consuming and IMHO useless: after a clean Eclipse shut-down, on the next start STS shouldn't refresh the dependencies, unless I tell it to do.
While the Gradle build is in progress, I notice that, for those projects, the library containing the Gradle external dependencies is called "com.springsource.sts.gradle.classpathcontainer" instead of "Gradle Dependencies (persisted)". When the build completes, then the library name turns to "Gradle Dependencies".
So, it seems like STS is not always persisting the Gradle Dependencies library configuration. Which is the criteria for this to occur?
Real case example: I just started and closed Eclipse repeatedly for 4 times now, always on the same workspace, and:
- the first three times, STS refreshed the dependencies of some of the projects at startup
- the fourth time STS did not refresh the dependencies of any project