AssertionErrors are silently swallowed somewhere inside the Subscriber implementation, we wont even get a log message about them.
New
Assertion error are logged in the runtime Eclipse Instance.
Also StackTrace for all Exceptions are printed to the parent Eclipse Instance, such that they are clickable. The logs in the runtime Eclipse insance are not clickable, which makes it painfull for debugging.
Misc
The switch from Exception to Throwable was necessary, as Throwable is the smallest common supertype of AssertionError and Exception.
Current
AssertionErrors are silently swallowed somewhere inside the Subscriber implementation, we wont even get a log message about them.
New
Assertion error are logged in the runtime Eclipse Instance. Also StackTrace for all Exceptions are printed to the parent Eclipse Instance, such that they are clickable. The logs in the runtime Eclipse insance are not clickable, which makes it painfull for debugging.
Misc
The switch from
ExceptiontoThrowablewas necessary, asThrowableis the smallest common supertype ofAssertionErrorandException.