If you are on unix, you could copy your deployment into a different location in
the same filesystem when ./deploy is, then do an atomic 'move'.
We would need to look what changed from 3.0.6 to 3.2.8.
View the original post :
Apparently not finding the application.xml isn't necessarily the problem. I
just did a new build and the application.xml was again not found, but the
scanning failed error didn't come up. In fact, 3.2.8 picked up the
application.xml file shortly thereafter and deployed my ear correctly.
I
