Assume you have a Gradle multiproject and that it is under version control.
Suppose this project is already an Eclipse project and all the Eclipse metadata files (.project, .classpath, .settings folder, etc.) are under version control.
You check it out in a folder and then use the STS Gradle Import Wizard to import in a new repository.
Suppose you UNCHECK all the following: run before, run after and create resource filters.
You do that because you know that all the necessary data are already there, because the whole thing is under version control: so, you just want to "mount" the main project and all the subprojects into the workspace. (note: ideally, you may use the standard Import Existing Project into workspace, but you can't because the main project, which is at the root of the Gradle multiproject, is hiding the subprojects).
After the import process has finished, even if you chose not to do anything special, you'll see some outgoing changes in the workspace:
- .settings/com.springsource.sts.gradle.core.prefs for all the subprojects: they have outgoing changes because the import wizard changes the timestamp in the first line of the file, with the import time
- .settings/com.springsource.sts.gradle.core.import.prefs of the main project: same problem as above, the timestamp is updated
- .classpath of the main project: the order of the classpath entries is not predictable (I'll open a new issue for this)
So, my request is: avoid to change the timestamp in the prefs files (is the timestamp needed at all?) when you import the projects. Or, at least, avoid to change it if no changes to the prefs file is actually needed.