Okay, I gave this morning's nightly build a try, and I'm still seeing a timing issue between my JEP and the deployment scan. But the problem has moved. But first, congrats on making the nightlies boot up much much faster than CR2 even. That's very pleasant. Now my analysis... The HDScanner in deploy/ helps, as it doesn't seem to trip over the .rails archive before it's recognizable as a vfszip. But there's still conf/bootstrap/profile.xml setting up and starting a VFSDeploymentScanner, which has inherited the scanning-deploy-too-soon issue I saw the other day with HDScanner. This non-hotdeploy, boot-time scan grabs myapp.rails with a FileHandler before my deployer has had its JEP triggered. It's still a bootstrap scanner iterating deploy/'s children before deployers/ has been fully install, I think. Having scan() wait at a barrier of some sort until the DEPLOYERS phase is complete would seem a possible solution. Thoughts? -Bob View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4193469#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...