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

[Martin Malina (JIRA)]

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

Martin Malina commented on JBIDE-18862:
---------------------------------------

[~rob.stryker], I think it does not work 100 %. The markers are mostly removed after undeploying, that's fine.
But the case where the *.dodeploy is already present is not ok - the tooling should remove it first before copying the content over, but it doesn't.
So when you deploy an ear module to wildfly, the content is being copied while the *.dodeploy flag is there.
That's not a problem with a stopped server, but if the server is running, this will result in unexpected behavior:
This will be in the log:
{code}
16:33:07,134 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-9) JBAS015876: Starting deployment of "earproj.ear" (runtime-name: "earproj.ear")
16:33:07,157 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-10) JBAS015973: Starting subdeployment (runtime-name: "dynproj.war")
16:33:08,013 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-6) JBAS017534: Registered web context: /dynproj
16:33:08,053 INFO  [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS018559: Deployed "earproj.ear" (runtime-name : "earproj.ear")
{code}
So it seems it's already deployed. But in fact the file are still being copied and eclipse status bar at the bottom right is showing the progress.
So really you should always check if the marker is there and if so, remove it.
Also, I had issues deploying my big module, but that's for another JIRA - JBIDE-19043

Also, when I remove a deployed ear module from a running server, I will end up with the .undeployed marker. I thought we concluded that this should be removed as well, right?

> 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)