Ethan Atkins 031e9463da Improve error reporting for classloading issues ... We noticed that the community build was failing for some projects due to some class loading issues. My initial approach for detecting the errors didn't always work because the test framework might wrap the underlying exception. To fix that, I add the causes to the list of throwables to scan for class loading related exceptions. I also added ClassNotFoundException to the list of types to check for. I additionally added more context to the error message so that it is more clear to the user what specifically went wrong. The error message is intended to provide examples that the user can actually paste into the console. There is also a lot of manual line wrapping that could be improved by defining paragraphs and then splitting on the jline terminal width. That could be a useful internal helper function to improve our log messages in general. The underlying issue could be addressed by allowing the user to specify libraries that get excluded from the dependency classpath for layering purposes. I'm not sure the best way to do that yet and adding that feature wouldn't fix any existing builds so I think that would be better handled in 1.4.0.		2019-04-03 11:02:49 -07:00
..
src	Improve error reporting for classloading issues	2019-04-03 11:02:49 -07:00
NOTICE	Add, configure & enforce file headers	2017-10-05 09:03:40 +01:00