I just ran another Maven build and all tests passed. So this is another random failure due to recent changes, arg.
Gary On Wed, May 21, 2014 at 3:40 PM, Matt Sicker <[email protected]> wrote: > The test might be taking liberties with how it expects the runtime to > behave. You might be on to something. Though log4j-core doesn't use forks. > > > On 21 May 2014 14:18, Gary Gregory <[email protected]> wrote: > >> Failed tests: >> LoggerTest.testReconfiguration:210 Reconfiguration failed expected not >> same >> >> Which ran fine from Eclipse. >> >> I am wondering if this is due to the recent fork mode for tests in the >> build? >> >> From Eclipse, the test class ran fine by itself. >> >> 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
