Norman Maurer e845670043 Set some StackTraceElement on pre-instantiated static exceptions ... Motivation: We use pre-instantiated exceptions in various places for performance reasons. These exceptions don't include a stacktrace which makes it hard to know where the exception was thrown. This is especially true as we use the same exception type (for example ChannelClosedException) in different places. Setting some StackTraceElements will provide more context as to where these exceptions original and make debugging easier. Modifications: Set a generated StackTraceElement on these pre-instantiated exceptions which at least contains the origin class and method name. The filename and linenumber are specified as unkown (as stated in the javadocs of StackTraceElement). Result: Easier to find the origin of a pre-instantiated exception.		2016-06-20 11:33:05 +02:00
..
src	Set some StackTraceElement on pre-instantiated static exceptions	2016-06-20 11:33:05 +02:00
pom.xml	Make JCtools available (provided scope) for tests and optional OSGI, issue #5383	2016-06-11 07:15:48 +02:00