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

[Rob Stryker (JIRA)]

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

Rob Stryker commented on JBIDE-18862:
-------------------------------------

> Also, I'm not sure that ever deleting an .isdeploying marker is ever appropriate.

This is referring to the case of a running server. Obviously a stopped server is more likely to be a stale .isdeploying marker.   The problem is, the same logic is used against remote servers as for local, and the 'externally managed' checkbox means we never *really* know if the remote server is up or down. I'm trying to fix that in another bug, but when 'externally managed' is checked we don't *really* know. We don't necessarily have a reference to a remote process if it was started externally, and so we can't check if the remote process exists or what. 

> 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: Feature Request
>          Components: server
>         Environment: Windiws7 64bit, JDK 8u25
>            Reporter: Darryl Miles
>            Priority: Minor
>             Fix For: 4.2.2.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)