Today, we have released Buildship 1.0.16. The new release brings better WTP integration and several usability improvements. This release is based on Gradle 2.14 which comes with many improvements of itself.
Correct classpath for WTP projects
Eclipse WTP requires dependencies to be annotated to determine whether they should be packed into the
.war file and deployed to the server or not. This information is provided by Gradle 2.14 and above and Buildship makes use of it.
This means that Buildship can now be used for developing WTP projects as long as users check in the component and facet configuration files. Their creation will be automated in future Buildship versions.
Gradle user home is now a workspace preference
The Gradle user home directory can now be configured in the workspace preferences. It has been removed from the project import wizard and run configuration page. This makes importing projects more convenient and allows sharing the configuration files even if you have a custom Gradle user home.
Please note that we do not plan to add workspace preferences for the Java home, JVM arguments and Gradle program arguments. These can all be set in the gradle.properties file in your Gradle user home.
“Add Gradle Nature” action for existing projects
Some tools like the Git and SVN plugins for Eclipse do not allow users to run the Gradle import wizard at the moment. The best way of importing such a Gradle project was to open the import wizard and manually navigate to the checkout location.
This is no longer necessary. You can now select the “Import as general project” option and then use the new “Add Gradle Nature” action. This will synchronize the project just as if you had imported it using the Gradle import wizard.
If you would like to improve the situation further, please vote for this enhancement request for EGit.
“Refresh Gradle Project” shown in Gradle editor
The “Refresh Gradle Project” was only available when right-clicking on a project. It is now also shown when right-clicking on any
.gradle file as well as in the context menu of the Gradle editor.
Gradle classpath container is restored if missing
When converting an existing Eclipse Java project to Gradle, the Gradle classpath container was missing. It is now always added when a project is a Java project.