[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=13026715#comment-13026715 ] 

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

My tests are showing the possibility for uncertainty when removing a do-deploy for the case of an incremental publish, especially when the server is minimizing redeployments (ie server is in debug mode). The scenario appears like this:

1) server starts up in debug mode
2) eclipse has a full-publish of a module
3) eclipse has another incremental publish of  the  module before the server has managed to pick up the full publish
4) The incremental publish deletes the .dodeploy,  then copies its delta / changes over
5) The .dodeploy is not added again, since the server is trying to minimize redeployments
6) The module is never picked up by the server. 

At this point I think it's most wise to simply remove the .dodeploy during or after a remove operation. 


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