[ https://issues.jboss.org/browse/WFLY-8697?page=com.atlassian.jira.plugin.... ] Stuart Douglas commented on WFLY-8697: -------------------------------------- This is not possible without a major rework of the DUP process, that would come with a significant memory cost. For some deployment processors this is simple, they add something to the DeploymentUnit, so undeploy can simply remove it, however for most of them it is not nearly this simple as they mutate data structures rather than just adding something. This would mean they would need to 'undo' what that have done, which in general would require a lot more book keeping, as they essentially need to store the state pre modification, which has a significant runtime memory cost. This is why the deployment is restarted on a dependency change, because even though we could force undeploy to be the opposite of deploy it is both very error prone and comes with a big runtime memory cost. -- This message was sent by Atlassian JIRA (v7.2.3#72005)