[
https://issues.jboss.org/browse/JBIDE-18862?page=com.atlassian.jira.plugi...
]
Rob Stryker resolved JBIDE-18862.
---------------------------------
Resolution: Done
Everything [~dlmiles] says is relevant and I've opened
https://issues.jboss.org/browse/JBIDE-19182 to track that issue.
I believe this issue specifically (marker files when deleting a module) has been solved.
[~mmalina] also had a niche case that I feel doesn't apply to this jira directly and
would be better tracked in the new one.
Pushed to maintenance.
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.Beta1, 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)