[jbosstools-issues] [JBoss JIRA] (JBIDE-26740) add option to Wildfly-Overview to "auto-restart" after publishing

nimo stephan (Jira) issues at jboss.org
Fri Jul 26 18:21:00 EDT 2019


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

nimo stephan edited comment on JBIDE-26740 at 7/26/19 6:20 PM:
---------------------------------------------------------------

Could you make a FR (Feature Request) at the WTP level, as you are better involved in this and know what has to be changed. 

It makes sense that "Every change in deployment should trigger a wildfly restart automatically."..especially while developing. Having an option for this would be good. Doing the restart manually is awkward..


was (Author: nimo22):
Could you make a FR (Feature Request) at the WTP level, as you are better involved in this and know what has to be changed. 

It makes sense that "Every change in deployment should trigger a wildfly restart automatically." Having an option for this would be good. Doing the restart manually is awkward..

> add option to Wildfly-Overview to "auto-restart" after publishing
> -----------------------------------------------------------------
>
>                 Key: JBIDE-26740
>                 URL: https://issues.jboss.org/browse/JBIDE-26740
>             Project: Tools (JBoss Tools)
>          Issue Type: Feature Request
>          Components: server
>    Affects Versions: 4.12.0.Final
>            Reporter: nimo stephan
>            Priority: Critical
>
> Actually, with *Jboss Tools* we can change to automatically *publish* to Wildfly-Server after resources has changed. However, it makes sense *to restart the server automatically* after code/resource is changed and published. 
> Please add a new option in "Wildfly Server Overview" beneath the "Publishing" called "*Restarting*" with a checkbox. So when user checks "restart after publish", *server will be automatically restarted* after resources has changed.



--
This message was sent by Atlassian Jira
(v7.12.1#712002)


More information about the jbosstools-issues mailing list