[
https://issues.jboss.org/browse/JBIDE-18094?page=com.atlassian.jira.plugi...
]
Rob Stryker updated JBIDE-18094:
--------------------------------
Attachment: JBIDE-18094_dialog.png
JBIDE-18094.png
The two screenshots here show both the editor and the dialog respectively. Implementation
is very similar to Max's proposed dialogs.
When in debug mode, the regular expression will be ignored, and modules will only be
restarted if either the server is set to automatically restart modules on a hotcode
replacement failures, or the user initiates a full publish.
When in run mode, the regular expression will be respected and modules may be
force-restarted if a pattern match is found.
By default, our custom hotcode replacement will be enabled for JBoss servers. The above
dialog will pop up, showing all modules that will be restarted. The user is unable to
restart only a subset of the modules at this time, since we (so far) cannot accurately
determine which modules need to be restarted.
Users may also terminate the server, restart the server, or continue (basically ignore the
hotcode issue and leave the previously running module deployment active).
Do not force restart modules when server is run in debug mode
-------------------------------------------------------------
Key: JBIDE-18094
URL:
https://issues.jboss.org/browse/JBIDE-18094
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: server
Affects Versions: 4.2.0.Beta3
Reporter: Rob Stryker
Fix For: 4.2.0.CR1
Attachments: initialsuggestionfor_hotcodefailurereplace.bmml,
initialsuggestionfor_hotcodefailurereplace.png, JBIDE-18094.png, JBIDE-18094_dialog.png,
serversetting.bmml, serversetting.png, update_dialog_based_on_existing_hcr.bmml,
update_dialog_based_on_existing_hcr.png
The request is that modules should not force-restart when a server is in debug mode. More
often than not, a change to a .class file, when the server is in debug mode, does not
require any special action or force-restart of the module. The changes to the .class file
will be picked up automatically.
Ideally, we would also detect a hotcode replace failure, and then force-restart the
module if possible.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)