I honestly didn't think there would be a test verifying an exception for that scenario.
On 2 March 2016 at 21:12, Gary Gregory <[email protected]> wrote: > This is a case of a change made without adjusting the unit test methinks. > > G > > ---------- Forwarded message ---------- > From: Apache Jenkins Server <[email protected]> > Date: Wed, Mar 2, 2016 at 6:59 PM > Subject: Jenkins build is still unstable: Log4j 2.x #1753 > To: [email protected] > > > See <https://builds.apache.org/job/Log4j%202.x/changes> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [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]>
