[
https://issues.redhat.com/browse/JBIDE-26740?page=com.atlassian.jira.plug...
]
Robert Stryker commented on JBIDE-26740:
----------------------------------------
I'm rejecting this issue. But there's an alternative option for you.
Inside the server editor, you can set a 'restart pattern' for your deployments. It
won't restart the app server entirely, but it will restart the deployment. What that
means is instead of just restarting a deployment when a "full publish" is
requested by the user, we'll do it any time a specific restart pattern is matched.
So when you change a file, we'll copy the changes and add a .dodeploy marker to inform
the app server to completely reload the deployment (again, the deployment, not the
server).
Hope this helps.
add option to Wildfly-Overview to "auto-restart" after
publishing
-----------------------------------------------------------------
Key: JBIDE-26740
URL:
https://issues.redhat.com/browse/JBIDE-26740
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: server
Affects Versions: 4.12.0.Final
Reporter: nimo stephan
Priority: Critical
Fix For: 4.14.0.Final
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.13.8#713008)