Re: [jbehave-dev] Loggin in jbehave

2015-01-30 Thread Chris Aguirre
Following up on Mauro's response... We extended the *StoryReporter* class and added log messages in certain methods we wanted logged such as: *failed(String step, Throwable cause)* *successful(String step)* *beforeScenario(String scenarioTitle)* *etc...* Then we added this new

Re: [jbehave-dev] Loggin in jbehave

2015-01-29 Thread Mauro Talevi
The reporters do not by default include any logger output, except for logger configured to wrote to sysout and then only for the Console output. If you want to do some quick debugging this is the easiest way. Else, you can define your own custom logging-based reporter that includes any log s

Re: [jbehave-dev] Loggin in jbehave

2015-01-29 Thread Frank Pedroza
We addressed this need by introducing the LoggingStoryReporter as shown early on in the thread. This allowed us to continue capturing system outs to the console (yuck) but also capture all our logging in a separate file. We sent up 2 log4j appenders to do this. On Thu, Jan 29, 2015 at 1:56 AM, Om

[jbehave-dev] Loggin in jbehave

2015-01-29 Thread Omer Shem-Tov
Hi, I'm trying to add logging to jbehave, and I'm not sure what is the best practice. beside this discussion http://www.mail-archive.com/dev%40jbehave.codehaus.org/msg08872.html I didn't find any documentation. I'm trying to add log4j properties from a file, so when I log messages using logger.deb