[
https://issues.jboss.org/browse/JBIDE-25894?page=com.atlassian.jira.plugi...
]
Mickael Istria commented on JBIDE-25894:
----------------------------------------
To workaround the issue with JDT versions, I used the following command which seems to
properly install everything at one (from Eclipse Platform zip, nightly build
{quote}
$ ./eclipse -nosplash -consoleLog -application org.eclipse.equinox.p2.director -repository
http://download.eclipse.org/jdtls/snapshots/repository/latest/ -repository
http://download.eclipse.org/eclipse/updates/4.8-I-builds/I20180402-2000/ -repository
http://download.eclipse.org/releases/photon -repository
http://download.jboss.org/jbosstools/oxygen/development/updates/ -installIU
org.eclipse.jdt.ls.core/0.0.0 -installIU
org.jboss.tools.ws.jaxrs.feature.feature.group/0.0.0 -installIU
org.jboss.tools.cdi.feature.feature.group/0.0.0 -installIU
org.jboss.tools.maven.hibernate.feature.feature.group/0.0.0 -installIU
org.hibernate.eclipse.feature.feature.group/0.0.0 -installIU
org.eclipse.m2e.wtp.jaxrs.feature.feature.group/0.0.0
{quote}
I couldn't see Jax-RS contributing completion or warning because the Jax-RS plugin
requires UI Harness to startup, and UI Harness is not available in JDT-LS. So for Jax-RS,
it would require to first split the bundle into a UI and a non-UI part.
I tried to get CDI reporting something, but I didn't manage to get CDI error markers
even from JBoss Tools... So if anyone has an example project showing CDI warnings, please
share it so I can test. [~fbricon] maybe?
Evaluate providing Java EE support as jdt.ls extensions
-------------------------------------------------------
Key: JBIDE-25894
URL:
https://issues.jboss.org/browse/JBIDE-25894
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Reporter: Mickael Istria
Jdt-LS relies on JDT for most features.
WTP and JBoss Tools do extend JDT to provide additional features, such as Jax-RS
completion.
It would be worth investigating whether just adding a few bundles from wtp and JBoss
Tools into JDT-LS can turn JDT-LS into a powerful tool for Java EE as well, and to
evaluate what must and can be improved to enable it.
As a good Java EE support requires a good Java support first, it's very likely that
extending JDT-LS (on demand) for Java EE is the most productive and efficient way to have
a Java EE language-server.
As Jakarta EE moves to
Eclipse.org, there are some discussions to improve JEE tools in
Eclipse IDE and in general. So building on top of WebTools/JBoss Tools and allowing
webtools/jbosstools to run in JDT-LS wo uld fit in the community mindset and may attract
3rd-party contributors to Eclipse Webtools.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)