Jonah Graham 1b080ac87e Include the full stack trace in exception message ... The format of this error message used to look like: ```java Expected number (0) of Non-OK status objects in log differs from actual (1). Error while parsing /projC_testTripleDownwardV/h3.h. java.lang.reflect.InvocationTargetException Caused by: java.lang.reflect.InvocationTargetException Caused by: java.lang.AssertionError: Need to hold a write lock to clear result caches ``` and it was hard to impossible to identify what the cause is. The hope is that capturing this fuller stack trace into the log will make it easier to identify the problem. Part of #117		2022-11-07 10:04:20 -05:00
..
org.eclipse.cdt.core	fix omitted parentheses in extended ASM #134	2022-11-07 09:55:18 -05:00
org.eclipse.cdt.core.linux	Upgrade build.properties warnings to errors	2022-11-06 18:29:28 -05:00
org.eclipse.cdt.core.linux.aarch64	Upgrade build.properties warnings to errors	2022-11-06 18:29:28 -05:00
org.eclipse.cdt.core.linux.ppc64le	Upgrade build.properties warnings to errors	2022-11-06 18:29:28 -05:00
org.eclipse.cdt.core.linux.x86_64	Upgrade build.properties warnings to errors	2022-11-06 18:29:28 -05:00
org.eclipse.cdt.core.macosx	Upgrade build.properties warnings to errors	2022-11-06 18:29:28 -05:00
org.eclipse.cdt.core.native	Upgrade build.properties warnings to errors	2022-11-06 18:29:28 -05:00
org.eclipse.cdt.core.tests	Include the full stack trace in exception message	2022-11-07 10:04:20 -05:00
org.eclipse.cdt.core.win32	Upgrade build.properties warnings to errors	2022-11-06 18:29:28 -05:00
org.eclipse.cdt.core.win32.x86_64	Upgrade build.properties warnings to errors	2022-11-06 18:29:28 -05:00
org.eclipse.cdt.ui	Upgrade build.properties warnings to errors	2022-11-06 18:29:28 -05:00
org.eclipse.cdt.ui.tests	Delete settings.xml file at end of test	2022-11-07 10:04:20 -05:00
pom.xml	[releng] Bump versions for CDT 11.0.0	2022-10-03 12:42:37 -04:00