[
https://issues.jboss.org/browse/JBIDE-21933?page=com.atlassian.jira.plugi...
]
Rob Stryker commented on JBIDE-21933:
-------------------------------------
1) Start CDK in eclipse
2) Expand openshift connection, create a project
3) Create a java application, something like eap-basic-s2i (kitchensink basically)
4) Publish the application, make sure the app runs and is visible in web browser
5) Change an xhtml file, verify changes are made.
6) Change the body of a method inside a .java file. This is a non-breaking change, and HCR
should update future responses immediately.
7) Change a method signature. Verify that a hotcode-replace dialog appears and offers 3
options.
[openshift server] Wire up module-restart / republish for hot-code
replace
--------------------------------------------------------------------------
Key: JBIDE-21933
URL:
https://issues.jboss.org/browse/JBIDE-21933
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: openshift, server
Affects Versions: 4.3.1.CR1
Reporter: Rob Stryker
Assignee: Rob Stryker
Fix For: 4.3.1.CR1
I've made this a subtask because it is related to but not a core piece of enabling
module-restart. This jira is for allowing more options on hotcode-replace failure.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)