[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:comment-tabpanel&focusedCommentId=13027019#comment-13027019 ] 

Darryl Miles commented on JBIDE-18862:
--------------------------------------

Informing the user of a problem during publish, with details of the problem (not a "the publish failed" error message) actually helps get problems solved.  The alternative maybe that the user start/stop container, add/remove module, start/stop module multiple times over several minutes to try to reset the system to continue development.

It may also be useful to have an action to delete the *.isdeploying file from the IDE, this saves the user a trip to an outside application (file manager) to do this manually, helping to heelp workflow inside IDE.

The user can not take any action to fix a matter the IDE knows about but fails to inform the user.  The end result is that XYZ just isn't working.

Further to the above if the IDE knows the container is not running and *.isdeploying file exists, it can also consider it stale.



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