Chapter 4. Resolved issues and known issues

4.1. Resolved issues

See Resolved Issues for JBoss EAP XP 2.0.0 to view the list of issues that have been resolved for this release.

4.2. Known issues

See Known Issues for JBoss EAP XP 2.0.0 to view the list of known issues for this release.

The server installation directory on a bare-metal Windows platform

After you exit a bootable JAR that is running on a bare-metal Windows platform, the %userprofile%\AppData\Local\Temp\wildfly-bootable-server_XXX_ server installation directory, where XXX is the unique identifier of your bootable JAR server, is not automatically deleted, so you must delete the directory manually. If you set an installation directory with the --install-dir=<install dir> argument, you must delete the specified <install dir> installation directory instead of the TEMP directory.

Hot deploy and OpenShift server adapter

Hot deploy does not currently work with OpenShift server adapter. Red Hat is working on a fix.

To work around this issue, in the OpenShift Server Adapter Settings Server Settings window, clear Use inferred Pod Deployment Path and set the Pod Deployment Path field to /opt/eap/standalone/deployments/, as illustrated in the accompanying image.

Figure 4.1. Pod deployment fields

OpenShift Server Adapter Settings Sever Settings window showing workaround configuration

For further information, see https://issues.redhat.com/browse/JBIDE-27591.