[jbosstools-issues] [JBoss JIRA] (JBIDE-18094) Do not force restart modules when server is run in debug mode
Martin Malina (JIRA)
issues at jboss.org
Tue Sep 9 04:10:59 EDT 2014
[ https://issues.jboss.org/browse/JBIDE-18094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13000161#comment-13000161 ]
Martin Malina commented on JBIDE-18094:
---------------------------------------
[~rob.stryker], can you advice how to test this? I started WildFly 8.1 in debug mode, deployed a war project and changed a class. I think the deployment was updated, but that's the same behavior as with normal running servers. How can I get the hot code dialog? I've never seen it.
> 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
> Assignee: Rob Stryker
> Labels: affects_documentation, new_and_noteworthy
> 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)
More information about the jbosstools-issues
mailing list