[
https://jira.codehaus.org/browse/JBEHAVE-637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=283602#comment-283602
]
Paul Hammant commented on JBEHAVE-637:
--------------------------------------
I would 'new up' reporters where I need them.
However I could be misunderstanding the nature of the linkage between the two.
In a given a given run, for say "Console Output" how many times will
createStoryReporter(..) be called? Once per story? or Once per run?
I assume it is the latter, as the console remains constant for the duration of
the run. With the latter a single instance of ConsoleOutput spanning multiple
stories (say in parallel) could detangle the output so that it makes sense in
the shared output. Without that "whole run" view of the essential visitation
of the methods, a whole run style of reporting will not be possible.
> Eliminate Format as a factory for StoryReporter
> ------------------------------------------------
>
> Key: JBEHAVE-637
> URL: https://jira.codehaus.org/browse/JBEHAVE-637
> Project: JBehave
> Issue Type: Improvement
> Components: Core
> Reporter: Paul Hammant
> Fix For: 3.x
>
>
> StoryReporter is made by Format, and that feels an unnecessary OO separation.
> Making custom reporters is cumbersome as a result. Can we kill the Format
> class?
--
This message is automatically generated by JIRA.
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
