We are migrating Eclipse Gradle plugins from Spring STS to Buildship and it’s raised a concern with the way that Buildship modifies the classpath.
With our previous setup we had our several projects with their several Eclipse configuration files setup exactly as intended and under version control and STS simply brought in the gradle dependencies that the config files were expecting.
Now with Buildship (2.2) if I choose “Refresh Gradle Project” from the context menu it overwrites the classpath file, rewriting some dependencies like the JRE and blowing away others like my Tomcat library.
I understand that Gradle plugins like “eclipse” and “eclipse-wtp” exists to allow you to generate these config files as you like through Gradle but that is not a tool that we have required because as I mentioned we version our eclipse configs just the way we like them.
With Buildship is it required to now use these plugins? If so, why isn’t there an option to use Buildship in a minimal approach where it simply brings in dependencies and leaves existing configuration alone? I don’t relish the idea of spending a couple of days understanding the eclipse-wtp plugin configuration and writing code to mirror all the existing config files in our many projects just because Buildship won’t leave the classpath alone.