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

[Darryl Miles (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-18862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13034062#comment-13034062 ] 

Darryl Miles commented on JBIDE-18862:
--------------------------------------

If you are checking for *.isdeploying (which is also a server managed marker file).
Then yes you can remove a *.dodeploy marker that still exists from a previous publish that has not yet been actioned by the AS.

Multiple sequential publishes in the Eclipse are normal, the first might take 10 seconds to project build and publish the next 2 publish operations (due to editor file saves) might take 1 second for each to complete.  It is normal for the AS to not notice the *.dodeploy yet.

If the AS did notice then the publish operation (and has started to deploy) Eclipse should be blocking due to the *.isdeploying marker being down.  Since it should not be performing any file change operations in the deployment/ directory until there *.isdeploying market has been  removed by the AS.

> when removing a module from AS runtime marker files are not removed automatically
> ---------------------------------------------------------------------------------
>
>                 Key: JBIDE-18862
>                 URL: https://issues.jboss.org/browse/JBIDE-18862
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: server
>         Environment: Windiws7 64bit, JDK 8u25
>            Reporter: Darryl Miles
>            Assignee: Rob Stryker
>             Fix For: 4.2.3.Final, 4.3.0.Alpha1
>
>
> module removal does not delete the various marker files relating to it:
> *.undeployed
> *.dodeploy
> The same should be true when ADDING a module, it should clean out any marker files.
> Setup an deploy-inhibiting marker file to ensure it won't try to deploy it before the *.ear is full written.
> Write out the*.ear file.
> Then adjust the marker files as necessary to reflect the intended state of the module (if it should be started then remove the inhibiting marker file in the previous step).



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)