[
https://issues.jboss.org/browse/JBIDE-21711?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen commented on JBIDE-21711:
---------------------------------------------
I think there are three sub issues here:
a) enabling Restart in the context menu on modules.
Which for EAP style apps means putting a .dodeploy file next to the deployment.
b) Full publish should behave like local - which in case of EAP is afaik to resync all
files and put a .dodeploy file
c) Then finally is to wire up the hot code replace code as screenshotted above to hook in
to allow restarts for module
and for server. Restart of server is probably best to be a soft restart of the server
since a full restart would require the
docker container/pod to restart (slow)
Server Adapter: Need a way to restart modules
---------------------------------------------
Key: JBIDE-21711
URL:
https://issues.jboss.org/browse/JBIDE-21711
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: openshift
Affects Versions: 4.3.1.Beta2
Reporter: Fred Bricon
Priority: Critical
When doing hot code reload in an OpenShift deployed EAP server, changing a method
signature will make the debugger complain with
!http://content.screencast.com/users/fbricon/folders/Jing/media/623c96cc-ae62-441b-b498-a39d9cf9b563/00000322.png|width=650!
Triggering a full publish on the module is not sufficient.
We need to at least have a way to trigger a module restart
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)