Use Wild Web developer instead of Eclipse WTP

[vogella]

https://github.com/eclipse/wildwebdeveloper is currently developed by Red Hat with the intention to provide light-weight language server based support for JavaScript, JSon, etc.

I suggest you evaluate if this package can be used instead of Eclipse WTP.

The EPPs are also planning to do that https://bugs.eclipse.org/bugs/show_bug.cgi?id=544355

[vogella]

Update: Just learned from @mickaelistria that this migration was already done for the Eclipse packages. So you should also consider to switch.

[mickaelistria]

It's been done for the JavaScript package, not (yet) for the Enterprise Java package.
The reason is that we still need WTP for JSP and JSF support, and Wild Web Developer doesn't (and probably never will) support those.

[martinlippert]

I would love to replace large parts of WTP in the Spring Tools 4 for Eclipse distribution with the Wild Web Developer pieces (it is on my to do list for quite a while already), but I need to figure out all the dependencies among the various WTP features that we would still need.

[vogella]

@martinlippert thanks, looking forward to it.

[martinlippert]

Since there are no concrete plans to incorporate this into any STS 3.x distributions, I will move this over to the Spring Tools 4 issue tracker.

[martinlippert]

I am pulling this from the upcoming 4.4 release, this requires a bit more thought and testing. Ripping out the right pieces of the WTP tools and replacing them with the Wild Web tooling is a major change and probably needs more work.

One area that we need to investigate is the XML tooling that comes with the Wild Web package and whether we can use that as a full replacement of the existing tooling:

• make sure the project-related XML namespace resolution works with the new tooling (no idea yet how to integrate that)
• make sure the boot-ls contributed content-assist etc. works (should actually get easier with the Wild Web package due to everything being ls-based)

Other areas of work need to be identified and worked on. Nothing we can get done for the upcoming 4.4. release - unfortunately.