Details
Description
In revision 1280 XStream.InitializingException got replaced with a top level class:
But XStream still throws the deprecated XStream.InitializingException. This makes it impossible to catch the advertised new exception, client code still has to catch XStream.InitializationException.
Proposed fix: throw the top level InitializingException on all occurrences in class XStream or let XStream.InitializingException extend InitializingException.
Thanks for heads-up. Actually this got wrong by the refactoring. The inner exception is no longer in use now. Fixed in subversion.