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

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

This is a very nice dream to have, but until the app server has some type of incremental deployment API where "The AS is in control of all file changes to the deployment area itself", we're stuck with standard filesystem operations. 

If you seem to be more into your server adapter using management operations to communicate with the server, then I'd suggest when you create a server adapter, you configure it to either local+mgmt or rse+mgmt profiles.  These will use full management for deployments, but necessarily loses the possibility of incremental deployment to some extent. It's still quite fast when in local mode, but must send the entire zipped deployment over the wire when re-deploying large projects against an actual remote machine.  In these profiles, we don't use the filesystem to deploy at all, and do not deal with marker files at all. All deployments are done via the management API. 

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