Difference in Eclipse between Gradle Dependencies and Gradle Dependencies (persisted)

Question

I am a beginner in Gradle. What is the concept behind and the differences between Gradle Dependencies

and Gradle Dependencies (persisted) in Eclipse?

How can we get from one state to another and vice versa?

Answer 1

Gradle needs to know about the things that your project needs to build or run, in order to find them. We call these incoming files, the dependencies of the project. Moreover, Gradle needs to build and upload the things that your project produces. The Gradle Dependencies folder you are looking at has a list of all such dependencies(.jar files typically) gathered together.

Note that dependencies between projects and source folder configuration are stored in your project's metadata (the .classpath file). This means they will persist across Eclipse sessions.

Since 2.7.M2 the contents of the classpath container is also persisted in your workspace metadata. This reduces the time it takes for the IDE to become responsive when it starts up. However, it means you may need to manually trigger a refresh once in a while. You can tell whether a container was initialized from persisted state because it will be labelled as it's name is, under the Gradle Dependencies (persisted).

That's the only difference. One is Persisted, the other is not.

Hope this helps.