[jbosstools-issues] [JBoss JIRA] (JBIDE-18862) when removing a module from AS runtime marker files are not removed automatically

[ https://issues.jboss.org/browse/JBIDE-18862?page=com.atlassian.jira.plugi... ] Darryl Miles edited comment on JBIDE-18862 at 12/2/14 7:15 AM: --------------------------------------------------------------- The AS does emit a info/warning in server.log when an unexpected marker file exists. So if *.dodeploy is the only marker file that JBIDE creates. Then please take this bug to ensure that: * When REMOVING a module from runtime the *.dodeploy file is also deleted by Eclipse. [This is a bug right now] * Before ADDING a module to runtime, but before writing the EAR (or other module implementation data), ensure the *.dodeploy file is deleted by Eclipse. You delete it to prevent cross-over from a failed REMOVE and to ensure Eclipse doesn't process it. [Difficult to see/test as publishing can be too quick] * Before ADDING a module to runtime, but before writing the EAR (or other module imlementation data), ensure the target toplevel name/file is deleted. This would be "rm -rf ear-0.0.1-SNAPSHOT.ear.ear\" (as an exploded directory) or maybe "rm -f foobar-0.0.1-SNAPSHOT.ear" (as a file). This is to ensure a CLEAN is done before anything is written. Maybe server tooling already does this? [This appears to be the case in a quick test with exploded directory deployment, but would be nice to have it confirmed by someone understanding the Eclipse/JBIDE code] * (only) After ADDING a module to runtime, then you can re-create the *.dodeploy at the point when everything is publish ok. [Sure I can see a file there each time I expect it] was (Author: dlmiles): The AS does emit a info/warning in server.log when an unexpected marker file exists. So if *.dodeploy is the only marker file that JBIDE creates. Then please take this bug to ensure that: * When REMOVING a module from runtime the *.dodeploy file is also deleted by Eclipse. * Before ADDING a module to runtime, but before writing the EAR (or other module implementation data), ensure the *.dodeploy file is deleted by Eclipse. You delete it to prevent cross-over from a failed REMOVE and to ensure Eclipse doesn't process it. * Before ADDING a module to runtime, but before writing the EAR (or other module imlementation data), ensure the target toplevel name/file is deleted. This would be "rm -rf ear-0.0.1-SNAPSHOT.ear.ear\" (as an exploded directory) or maybe "rm -f foobar-0.0.1-SNAPSHOT.ear" (as a file). This is to ensure a CLEAN is done before anything is written. Maybe server tooling already does this? * (only) After ADDING a module to runtime, then you can re-create the *.dodeploy at the point when everything is publish ok. -- This message was sent by Atlassian JIRA (v6.3.8#6338)