As Ant copies over files, if the hot deployer wakes up, it will check what files have been updated even if Ant is not finished. There is no way to coordinate Ant and the hot deployer. For production use, turn off the hot deployer. While this is a great developer feature I recommend not having it on for production. Do you really want who-knows-what being deployed to a production system? Additionally, consider the performance implications of having the hot deployer thread trash your CPUs cache and the thrash the disk every 5 seconds. If you must deploy something, and the hot deployer is off, you can always copy it to the deploy directory and then invoke the deployer manually (via JMX). This works for exploded archives as well as for packaged ones. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4006452#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...