[jbosstools-issues] [JBoss JIRA] (JBIDE-18094) Do not force restart modules when server is run in debug mode

[Rob Stryker (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-18094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12994268#comment-12994268 ] 

Rob Stryker commented on JBIDE-18094:
-------------------------------------

the balsamiq asks how this will affect openshift / deploy-only. It will not affect it at all. Deploy-only server does not use a java launch, and openshift has no launch at all. 

This may affect fuse tools, though. 

> 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
>         Attachments: initialsuggestionfor_hotcodefailurereplace.bmml, initialsuggestionfor_hotcodefailurereplace.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.2.6#6264)