[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:all-tabpanel ]

Darryl Miles updated JBIDE-18862:
---------------------------------
    Description: 
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).


  was:
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, adjust the marker files a necessary to reflect the intended state of the module (if it should be started then remove the inhibiting marker file in the previous step).




> 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
>
> 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.8#6338)