-
Bug
-
Resolution: Done
-
Major
-
None
-
None
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).
- is related to
-
JBIDE-18861 module start action does not delete *.undeployed file
-
- Closed
-
-
JBIDE-18860 Publish to Wildfly AS does not update files
-
- Closed
-
-
JBIDE-19182 Incremental Publish after Full Publish WRT dodeploy markers
-
- Closed
-