Hot deployment causes cascading redeployment of dependent artfacts when using jboss-all.xml configuration files --------------------------------------------------------------------------------------------------------------- Key: WFLY-10221 URL: https://issues.jboss.org/browse/WFLY-10221 Project: WildFly Issue Type: Bug Affects Versions: 11.0.0.Final Reporter: John Doe Assignee: Jason Greene Priority: Minor Let's assume I have 2 files _app.ear_ and _framework.ear_ deployed in WildFly 11. _framework.ear_ needs to be deployed before _app.ear_ which is expressed by the _jboss-all.xml_ file contained in the app.ear/META-INF folder: {code:java} <jboss umlns="urn:jboss:1.0"> <jboss-deployment-dependencies xmlns="urn:jboss:deployment-dependencies:1.0"> <dependency name="framework.ear" /> </jboss-deployment-dependencies> </jboss> {code} Now something changes in _framework.ear_ and a redeployment of _framework.ear_ becomes necessary. _app.ear_ does get redeployed, too, immediately after a hot deployment of _framework.ear_ has been carried out. *Observations:* After the redeployment of _framework.ear_ a new _framework.ear.deployed_ marker gets created, but same does not hold for _app.ear.deployed_. In fact no new _app.ear.deployed_ gets created at all (same timestamp for this file as before) despite a redeployment takes place. Nevertheless, in the console I see a redeployment for the dependent _app.ear_ occurs. Extending the example above, this is time consuming when you have a couple of additional dependencies cascading through. I don't understand why this happens because _app.ear_ did not change. My expectation is that only a redeployment of _framework.ear_ will take place. In my opinion there is no reason to redeploy _app.ear_, too.