[ https://issues.jboss.org/browse/JBIDE-18862?page=com.atlassian.jira.plugi... ] Darryl Miles commented on JBIDE-18862: -------------------------------------- We're talking about adding and removing JavaEE _MODULES_ here. So a full or incremental publish aspect should be irrelevant. The actions performed by Eclipse is the same, because there is no such thing as "removing a whole JavaEE module incrementally", there is only the concept of "remove the whole JavaEE module". The deletion of the toplevel directory (or file, in the case of deploying as JAR) is not related to the concept of a "Full Publish" vs "Incremental Publish". When adding a module, the Eclipse AS driver should ensure the toplevel target is deleted, and it is not trying to publish over the top of a failed removal (possibly due to file locking). If the toplevel directory is not assured of being not-existing before the start of publish a warning should really be issued to the user, whom can "continue anyway", "abort the module add action". This is what my third point talks of. -- This message was sent by Atlassian JIRA (v6.3.8#6338)