[ http://jira.codehaus.org/browse/JBEHAVE-276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mauro Talevi updated JBEHAVE-276: --------------------------------- Summary: Clarify the Scenario Reporters example and API (was: Clearify the Scenario Reporters example and API) > Clarify the Scenario Reporters example and API > ---------------------------------------------- > > Key: JBEHAVE-276 > URL: http://jira.codehaus.org/browse/JBEHAVE-276 > Project: JBehave > Issue Type: Improvement > Components: Documentation > Affects Versions: 2.5.2 > Environment: Maven and Selenium > Reporter: Ricardo S.A. Silva > > The example for configuration of 'Scenario Reporters' on > http://jbehave.org/reference/stable/reports.html is not clear. The code > appear to be outdated and I am not able to use it. > One other point: Is it really necessary use 9 different classes just to save > my reports to a TXT file ? It's a common task and it will help a lot if it > was more simple. > (The classes on examples are: ScenarioNameResolver, > UnderscoredCamelCaseResolver, PropertyBasedConfiguration, ScenarioDefiner, > ClasspathScenarioDefiner, PatternScenarioParser, ScenarioReporter, > ScenarioReporterBuilder, FilePrintStreamFactory) > I really want to use JBehave, but the Factory/Definer/Builder hell is really > boring. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email