[ https://issues.jboss.org/browse/JBIDE-18862?page=com.atlassian.jira.plugi... ] Darryl Miles edited comment on JBIDE-18862 at 12/10/14 6:59 PM: ---------------------------------------------------------------- To go back to Rob's race concern: Eclipse can check *.isdeploying does not exist, before performing any kind of publish action that causes file/dir modification in the deployment area. This (*.isdeploying) is managed by the AS and will be removed and replaced with a *.failed or *.deployed file once a terminal cause has been reached of the currently in-progress deployment operation at the AS. Think of *.isdeploying as the AS's way of instructing Eclipse not to modify files just now, because the AS maybe opening/reading them. {{code}} BASENAME="blah.blah.ear" FILENAME="${BASENAME}.isdeploying" while test -f $FILENAME do Update Eclipse monitor description "Waiting for AS to remove $FILENAME marker file" while test -f $FILENAME && $loop < 10 do sleep 0.25 seconds $loop++ done Present dialog to user asking to continue waiting or abort operation done # at this point *.isdeploying does not exist if rm "${BASENAME}.dodeploy" then # re-test *.isdeploying again, using same logic as above (you can skip this re-test if you know the "rm -f" did not remove any file, this maybe possible as the unlink() system call has an error code when the file being deleted did not exist. fi # Update eclipse progress monitor description to relate to publish action # there can technically still be a race but the chances of it happening are a small as possible, when you are not getting a positive acknowledgement back from the AS, that would act like a synchronization point ## do publish stuff if eclipse_module_is_set_to_start then touch $FILENAME fi {{code}} was (Author: dlmiles): To go back to Rob's race concern: Eclipse can check *.isdeploying does not exist, before performing any kind of publish action that causes file/dir modification in the deployment area. This (*.isdeploying) is managed by the AS and will be removed and replaced with a *.failed or *.deployed file once a terminal cause has been reached of the currently in-progress deployment operation at the AS. Think of *.isdeploying as the AS's way of instructing Eclipse not to modify files just now, because the AS maybe opening/reading them. BASENAME="blah.blah.ear" FILENAME="${BASENAME}.isdeploying" while test -f $FILENAME do Update Eclipse monitor description "Waiting for AS to remove $FILENAME marker file" while test -f $FILENAME && $loop < 10 do sleep 0.25 seconds $loop++ done Present dialog to user asking to continue waiting or abort operation done # at this point *.isdeploying does not exist if rm "${BASENAME}.dodeploy" then # re-test *.isdeploying again, using same logic as above (you can skip this re-test if you know the "rm -f" did not remove any file, this maybe possible as the unlink() system call has an error code when the file being deleted did not exist. fi # Update eclipse progress monitor description to relate to publish action # there can technically still be a race but the chances of it happening are a small as possible, when you are not getting a positive acknowledgement back from the AS, that would act like a synchronization point ## do publish stuff if eclipse_module_is_set_to_start then touch $FILENAME fi -- This message was sent by Atlassian JIRA (v6.3.8#6338)