All components - including monitors - are configurable so you can swap the default with your own:
http://jbehave.org/reference/stable/configuration.html What use case are you trying to satisfy? Having say debug-level logging being always written to a file in the background? > On 12 May 2014, at 19:21, Frank Pedroza <[email protected]> wrote: > > Could you help me understand this a bit more or point me to something that > explains how I would configure the jbehave framework to support this? > > >> On Fri, May 9, 2014 at 4:12 PM, Mauro Talevi <[email protected]> >> wrote: >> JBehave uses the monitor pattern that allows you to honour dependency >> injection properly. Most logging frameworks rely on static lookup >> mechanisms. >> >> If you want to use a logging framework you can still do so by providing a >> logging implementation of the relevant interfaces. >> >> Cheers >> >> > On 9 May 2014, at 22:09, Frank Pedroza <[email protected]> wrote: >> > >> > I'm new to the group so sorry if this isn't the right venue for this sort >> > of question or if this has already been addressed, but why is any of the >> > JBehave framework using System.out rather than something like slf4j? >> >> --------------------------------------------------------------------- >> To unsubscribe from this list, please visit: >> >> http://xircles.codehaus.org/manage_email > > > > -- > -------------------------------------------- > Frank M. Pedroza - Software Engineer > Partnet - Development > 801.708.5050 > > ----------------------------------------------------------------- > The nice part about being a pessimist is that you are constantly being either > proven right or pleasantly surprised. > -- George F. Will
