[
https://issues.jboss.org/browse/JBIDE-18862?page=com.atlassian.jira.plugi...
]
Martin Malina closed JBIDE-18862.
---------------------------------
I checked some use cases with JBDS 8.1.0.CR1 and 9.0.0.Alpha1, most notably that a
dodeploy marker is removed when you publish to a stopped server and then remove the
deployment before you start the server. And I believe that we're good to close this
JIRA now. The special use case of incremental publish after full publish is tracked in
JBIDE-19182 .
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)