Closed bschinzel closed 2 years ago
I'm not able to replicate this, at least on my operating system. I have a command line utility that does the beginning work of creating a server to verify that the server is recognized properly. It's in the rsp-server repository.
search path /home/rob/apps/jboss/unzipped/jboss-eap-7.4.0.zip.expanded/jboss-eap-7.4 Beans: jboss-eap-7.4,EAP,7.4,/home/rob/apps/jboss/unzipped/jboss-eap-7.4.0.zip.expanded/jboss-eap-7.4
I'm going to suspect that this issue is out of date and will close it as such.
Using Server Connector v0.23.10:
When adding a JBoss EAP 7.4.0.GA home directory as a server it is detected as "org.jboss.tools.rsp.server.typeId": "org.jboss.ide.eclipse.as.eap.60".
When starting with Java 11 ("vm.install.path": "C:\JDK\java-11-openjdk-11.0.10.9-1.windows.redhat.x86_64"), the following error message is shown: "Unable to start the server: Extension backend error - server can not be started: server dahstat is not compatible with discovered java version 11.0.10".
I would expect EAP 7.4 to start with Java 11.