[jbosstools-issues] [JBoss JIRA] (JBIDE-17395) Run on server does not work if server is stopped (management operations)

[ https://issues.jboss.org/browse/JBIDE-17395?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-17395. --------------------------------- Resolution: Done The client (which opens the web browser, basically), already waits for a few things. 1) It waits for server to be started 2) It waits for the server to respond that the module is deployed properly via mgmt request The workflow of what's happening here is: 1) Run as -> Run on server 2) The server tries to publish, but is told by my delegate that we cannot publish to a stopped server 3) The server is started 4) The 'client' is given control, and waits for confirmation the module is ready The patch which has been committed will, during step 4), check if the module is 'synchronized'. In the above use case, the module is *not* synchronized, since we did not attempt to actually publish it. When the client learns the module isn't even synchronized, we issue a publish request. The result is pretty fast and looks good. Pushed to b3. -- This message was sent by Atlassian JIRA (v6.2.3#6260)