Currently touching descriptor files is the best way to redeploy an exploded deployment. Some deployment types do not require any descriptors, so there's no clear way to redeploy that deployment without removing it and adding it again. The workaround of course is to add a stub descriptor and touch that. Which brings to mind the following question: Does anyone think the deployment scanner should not only check for descriptor timestamp changes, but also check the module's folder's timestamp as well? For example, if the folder Blah.ear has a changed timestamp, is allowing the module to redeploy a good idea? I vote yes but I'm curious if there's some big reason why this isn't done already or if it's been tried before. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4244146#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...