Missing stack strace in warning logs make it hard to debug migration issues

Many warning messages only give the exception name. When it is a NullPointerException for instance, there's no way to find out where it comes from. I'd rather have an ugly but informative stack trace.

If an exception for a normal(-ish) or common condition is too verbose, maybe it shall be caught and specifically handled with a beautiful warning message instead.