Oh ok. :) On 13 February 2016 at 21:47, Gary Gregory <[email protected]> wrote:
> I made a silly mistake in the original version of the test. Fixed now. > Thanks Matt! > > Gary > On Feb 13, 2016 7:42 PM, "Matt Sicker" <[email protected]> wrote: > >> Oh, and all the Loggers in log4j-api unit tests are TestLoggers unless >> you override that system property in the test class. So nothing new to add >> support for that. >> >> On 13 February 2016 at 21:40, Matt Sicker <[email protected]> wrote: >> >>> It's set up as a custom log4j provider with a corresponding >>> LoggerContext and LoggerContextFactory. If you wanna use your own, you can >>> override the default via the system property log4j2.loggerContextFactory, >>> though I'm not sure that's what you're asking. >>> >>> On 13 February 2016 at 17:54, Gary Gregory <[email protected]> >>> wrote: >>> >>>> Hi All: >>>> >>>> Any hints on how to hook up a new logger to work like a TestLogger in: >>>> >>>> >>>> org.apache.logging.log4j.LoggerTest.flowTracingString_ObjectArray2_ParameterizedMessageFactory() >>>> >>>> ? >>>> >>>> Thank you, >>>> 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]> >>> >> >> >> >> -- >> Matt Sicker <[email protected]> >> > -- Matt Sicker <[email protected]>
