Remko thinks he knows what might have caused the issue and commented on the bug in jira.
On 8 March 2016 at 10:57, Gary Gregory <[email protected]> wrote: > It does not behave properly in 2.5 based on what I say. I did not try > master though, needs investigation... later today or tonight hopefully > unless you get to it first. > > Gary > > On Tue, Mar 8, 2016 at 6:56 AM, Matt Sicker <[email protected]> wrote: > >> I thought parameterized messages already checked the last param for >> exception. If it's not being printed out, that sounds like a bug! >> >> On 7 March 2016 at 22:29, Gary Gregory <[email protected]> wrote: >> >>> I've see this pattern: >>> >>> LOGGER.error("Error parsing {}", configSource.getLocation(), e); >>> >>> Which hides the exception. I changed it to: >>> >>> LOGGER.error("Error parsing " + configSource.getLocation(), e); >>> >>> I think we need something like: >>> >>> error(Throwable, String, Object...) >>> >>> Gary >>> >>> -- >>> E-Mail: [email protected] | [email protected] >>> Java Persistence with Hibernate, Second Edition >>> <http://www.manning.com/bauer3/> >>> JUnit in Action, Second Edition <http://www.manning.com/tahchiev/> >>> Spring Batch in Action <http://www.manning.com/templier/> >>> Blog: http://garygregory.wordpress.com >>> Home: http://garygregory.com/ >>> Tweet! http://twitter.com/GaryGregory >>> >> >> >> >> -- >> Matt Sicker <[email protected]> >> > > > > -- > E-Mail: [email protected] | [email protected] > Java Persistence with Hibernate, Second Edition > <http://www.manning.com/bauer3/> > JUnit in Action, Second Edition <http://www.manning.com/tahchiev/> > Spring Batch in Action <http://www.manning.com/templier/> > Blog: http://garygregory.wordpress.com > Home: http://garygregory.com/ > Tweet! http://twitter.com/GaryGregory > -- Matt Sicker <[email protected]>
