[ https://issues.jboss.org/browse/JBIDE-15357?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-15357: ------------------------------------- An additional publish click wipes out the deployment. The question is, why is this happening. My tests have revealed that it is calling an API I don't recall seeing "shouldIgnorePublishRequest()" which basically says, if the module has a project, and the project is not accessible, do not publish this. This wtp code seems to be intended to ensure that if you close your project, it won't be removed from the remote server entirely, and will instead be ignored. However, the instance of the module being passed in after a delete operation still has a project, which is not accessible. It isn't closed, though, but does not exist. So, it seems we'll need to override this method and say, if the module has a project, AND the project exists, AND it is not accessible (therefore, closed), it can be published (aka removed). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira