I heard in the Buildship Bug Tracker, that the Eclipse WTP support should have been greatly improved with Gradle 3. Now I wanted to play a little with Gradle 3.0-milestone-2, Eclipse NEON and Buildship 1.0.16. I created a folder and some files by hand and tried the Buildship importer. The current…

Hi Martin, Buildship 1.0.16 now correctly handles the classpath attributes on WTP projects. This means that e.g. provided or testCompile dependencies are no longer deployed to the server when running in Eclipse. Buildship 1.0.16 does not yet handle the facets and deployment assembly configuration.…

I have uploaded a new version to the GitHub repo named above. At the moment, I test with Eclipse Neon, BuildShip 1.0.21 and Gradle 3.2. All above steps are now working out of the box for a web project, that does not need files from another parallel project. :+1: The new test case covers a Test cl…

You need to apply the eclipse-wtp plugin to utility projects. Then they will be configured correctly.

Yes, looks like… I thought it would also set jst.web , but because of the missing apply plugin: ‘war’ it obviously does not. apply plugin: 'eclipse-wtp' eclipse { wtp { facet { facet name: 'jst.utility', version: '1.0' } } } The above build.gradle from the API project works as expected. T…

By the way, if there is anything else that you think the eclipse-wtp plugin should do differently, please let us know. We don’t have a lot of WTP experience and are always grateful for more insight. For instance: Why did you have to add that facet declaration? Looks to me like that should be a defa…

Yes Stefan, you are right. For Utility Module one does not need to specify the facet. The following build.gradle is enough: apply plugin: 'eclipse-wtp' Which still strikes me: the file .settings/org.eclipse.wst.common.project.facet.core.xml still contains installed facet=“jst.web” version=“2.4” …

[image] MBurchard: the file .settings/org.eclipse.wst.common.project.facet.core.xml still contains installed facet=“jst.web” version=“2.4” although it was set up as 3.1 by Gradle. It conaints two entries Even after running cleanEclipse? The eclipse tasks are currently adding things, but not r…

[image] st_oehme: [image] MBurchard: the file .settings/org.eclipse.wst.common.project.facet.core.xml still contains installed facet=“jst.web” version=“2.4” although it was set up as 3.1 by Gradle. It conaints two entries Even after running cleanEclipse? The eclipse tasks are currently ad…

I think we don’t add the JS nature, because we have no JavaScript support in the war plugin. So there would be no point activating it in Eclipse if it doesn’t work in the build. Of course you can always add this nature in eclipse.project.natures. The duplicate facet is interesting, I’ll have a look…

Improve Eclipse WTP support in Gradle 3, HowTo?

Help/Discuss

st_oehme (Stefan Oehme) September 1, 2016, 6:27pm 3

WTP support is coming, read more here: [Request for feedback] WTP support coming to Buildship

Topic		Replies	Views
Buildship 1.0.21 is now available Buildship buildship-release	12	6059	October 27, 2016
WTP currently does not support mixed deployment paths Buildship	28	6343	December 9, 2016
[Request for feedback] WTP support coming to Buildship Buildship	9	4841	September 10, 2016
No facets in project created with 1.0.10 Buildship	2	1662	September 1, 2016
Eclipse WTP + Gradle Buildship not deploying all project dependencies Buildship issue-resolved , buildship , eclipse	4	8684	November 23, 2016

Improve Eclipse WTP support in Gradle 3, HowTo?

Related topics