[ https://issues.jboss.org/browse/JBIDE-21857?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-21857: ---------------------------------- Steps to Reproduce: ASSERT: Have a running OpenShift java application on OpenShift with a server adapter. For example the one instantiated by eap64-basic-template. EXEC: Create a new OpenShift 3 server adapter for the application. EXEC: Restart server adapter in debug mode. EXEC: Rename method or add a field to class. ASSERT: Dialog warning about failed HCR is shown. EXEC: Reload the module. EXEC: Make change HCR compatible (e.g. method body). RESULT: HCR compatible change hasn't take effect. EXPECTED RESULT: Upon module restart and HCR compatible change this change will be visible, debugger get back to sync. was: ASSERT: Have a running OpenShift java application on OpenShift with a server adapter. For example the one instantiated by eap64-basic-template. EXEC: Create a new OpenShift 3 server adapter for the application. EXEC: Restart server adapter in debug mode. EXEC: Rename method or add a field to class. ASSERT: Dialog warning about failed HCR is shown. EXEC: Reload the module. EXEC: Make change HCR compatible (e.g. method body). RESULT: HCR compatible change hasn't take effect. EXPECTED RESULT: Upon module restart and HCR compatible change this change will be visible. Rename a private method in a class Observe: you get a dialog saying the HCR has failed and offering to reload the module Reload the module Now make a further change that is HCR-compatible (add a printf) Observe: the HCR works. -- This message was sent by Atlassian JIRA (v7.2.3#72005)