[jbosstools-issues] [JBoss JIRA] (JBIDE-18862) when removing a module from AS runtime marker files are not removed automatically
[
https://issues.jboss.org/browse/JBIDE-18862?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen commented on JBIDE-18862:
---------------------------------------------
we can't know if the .isdeploying is a something the server is actually doing or a
left over from a dead server.
Use putting content into the deployment via incremental updates should not be blocked by
ongoing deployment IMO
and actually it is never going to add a .deployed or .failed for incremental deployments
since incremental deployments are *not* triggering anything on the server since we are not
putting any .dodeploy file there. it is purely for updating html/css/etc. files.
I'm failing to see what the advanced and user interrupting logic above will solve/help
?
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)