Sort of an interesting idea, but it seems we could at least in the
testing scenario somehow keep a list of failed deployments.
Then upon lookup of one of these failed deployments print out the
issues that caused the app not to deploy as part of the message inside
the NameNotFoundException.
Just trying to find a way to prevent people from thinking that
NameNotFoundException is itself the problem. The message already says
that it is likely due to deployment failure and that they should
check, but clearly this is not enough.
-David
