[ https://issues.jboss.org/browse/JBIDE-18862?page=com.atlassian.jira.plugi... ] Darryl Miles commented on JBIDE-18862: -------------------------------------- Informing the user of a problem during publish, with details of the problem (not a "the publish failed" error message) actually helps get problems solved. The alternative maybe that the user start/stop container, add/remove module, start/stop module multiple times over several minutes to try to reset the system to continue development. It may also be useful to have an action to delete the *.isdeploying file from the IDE, this saves the user a trip to an outside application (file manager) to do this manually, helping to heelp workflow inside IDE. The user can not take any action to fix a matter the IDE knows about but fails to inform the user. The end result is that XYZ just isn't working. Further to the above if the IDE knows the container is not running and *.isdeploying file exists, it can also consider it stale. -- This message was sent by Atlassian JIRA (v6.3.11#6341)