After importing Gradle projects, I find org.eclipse.jdt.groovy.core.prefs in any prj
I have the following situation.
Consider a Gradle multiproject checked out from SVN.
This Gradle multiproject is set up for the use with STS 2.9.x.
Then, I import this multiproject in my new workspace using the "Import | Gradle project" wizard of STS 3.1.0.
In the import wizard dialog, I ONLY check "Enable dependency management", nothing else. Then I choose to import the whole Gradle multiproject.
After the import operation has finished, I find that the legacy STS projects are converted to 3.x format (that is: some com.springsource.* preferences are renamed to org.springsource.*). So far so good.
The strange thing is that a new file (org.eclipse.jdt.groovy.core.prefs placed in .settings folder) is added to ALL the Eclipse projects. This happens also for Java projects that DO NOT have the Groovy nature. I already checked that for those project:
- Groovy nature is missing
- Groovy libraries are not in the build path
- Gradle DSL support is disabled
So, why do I find those files in those projects? The contents of those files is just: eclipse.preferences.version=1 and groovy.compiler.level=18.
Who is responsible of the creation of those files? Is it Greclipse? If so, how is it possible, considering that the Groovy nature is missing on those projects? Is Greclipse in some way "enabled" on those projects all the same?
Thanks in advance,