[jbosstools-issues] [JBoss JIRA] (JBIDE-21857) Hot code replacement doesn't work on OpenShift

[ https://issues.jboss.org/browse/JBIDE-21857?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21857: ------------------------------------- Steps to Reproduce: EXEC: Create a new OpenShift EAP 6.4 application. Open New OpenShift application wizard, select eap64-basic-s2i template, proceed to next wizard page, change CONTEXT_DIR param to helloworld, click Finish and let import application to your workspace once you are prompted. EXEC: Create a new OpenShift 3 server adapter for the application. ASSERT: There is a started server adapter for the application in Servers view. EXEC: Restart server adapter in debug mode. ASSERT: Server adapter is in debug mode, synchronized. ASSERT: Dialog warning about failed HCR is shown. EXEC: Click button Restart buttons in Hot Code Replace Failed dialog. ASSERT: Module is deployed on a remote server. RESULT: Debugger is out of sync. EXPECTED RESULT: Debugger is back to sync. EXEC: Make a HCR compatible change (in method body e.g. change returned message). EXEC: Save editor. RESULT: Hot Code Replace Failed dialog is shown. EXPECTED RESULT: Change is propagated successfully, there is no HCR Failed dialog and debugger is in sync. was: EXEC: Create a new OpenShift EAP 6.4 application. Open New OpenShift application wizard, select eap64-basic-s2i template, proceed to next wizard page, change CONTEXT_DIR param to helloworld, click Finish and let import application to your workspace once you are prompted. EXEC: Create a new OpenShift 3 server adapter for the application. ASSERT: There is a started server adapter for the application in Servers view. EXEC: Restart server adapter in debug mode. ASSERT: Server adapter is in debug mode, synchronized. EXEC: Expand server adapter. ASSERT: JMX is connected (bug JBIDE-21857, if it is disconnected, double click on the button and wait to connect). EXEC: Rename method or add a field to class (e.g. in HelloService) = do HCR incompatible change in class structure. EXEC: Save editor. ASSERT: Dialog warning about failed HCR is shown. EXEC: Click button Restart buttons in Hot Code Replace Failed dialog. ASSERT: Module is deployed on a remote server. RESULT: Debugger is out of sync. EXPECTED RESULT: Debugger is back to sync. EXEC: Make a HCR compatible change (in method body e.g. change returned message). EXEC: Save editor. RESULT: Hot Code Replace Failed dialog is shown. EXPECTED RESULT: Change is propagated successfully, there is no HCR Failed dialog and debugger is in sync. -- This message was sent by Atlassian JIRA (v7.2.3#72005)