[jbehave-dev] [jira] Commented: (JBEHAVE-543) Before/After Story/Scenario methods could accept parameters that have meaning at that moment

[ https://jira.codehaus.org/browse/JBEHAVE-543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=272629#comment-272629 ] Mauro Talevi commented on JBEHAVE-543: -- Adriano, I pulled your commits (except the one above)

[jbehave-dev] [jira] Work started: (JBEHAVE-543) Before/After Story/Scenario methods could accept parameters that have meaning at that moment

[ https://jira.codehaus.org/browse/JBEHAVE-543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JBEHAVE-543 started by Mauro Talevi. Before/After Story/Scenario methods could accept parameters that have meaning at that moment

[jbehave-dev] [jira] Work started: (JBEHAVE-540) ANSI-coded console output

[ https://jira.codehaus.org/browse/JBEHAVE-540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JBEHAVE-540 started by Mauro Talevi. ANSI-coded console output - Key: JBEHAVE-540 URL:

[jbehave-dev] [jira] Updated: (JBEHAVE-543) Before/After Story/Scenario methods could accept parameters that have meaning at that moment

[ https://jira.codehaus.org/browse/JBEHAVE-543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-543: - Component/s: Core Before/After Story/Scenario methods could accept parameters that have meaning

[jbehave-dev] [jira] Assigned: (JBEHAVE-540) ANSI-coded console output

[ https://jira.codehaus.org/browse/JBEHAVE-540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi reassigned JBEHAVE-540: Assignee: Mauro Talevi ANSI-coded console output -

[jbehave-dev] [jira] Updated: (JBEHAVE-551) Better integration with JUnit (Separate results for each story/scenario/example)

[ https://jira.codehaus.org/browse/JBEHAVE-551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-551: - Fix Version/s: 3.5 Assignee: Mauro Talevi Better integration with JUnit (Separate results

[jbehave-dev] [jira] Updated: (JBEHAVE-528) Examples Table for subset of steps

[ https://jira.codehaus.org/browse/JBEHAVE-528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-528: - Fix Version/s: (was: 3.5) 3.x Examples Table for subset of steps

[jbehave-dev] [jira] Commented: (JBEHAVE-551) Better integration with JUnit (Separate results for each story/scenario/example)

[ https://jira.codehaus.org/browse/JBEHAVE-551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=272643#comment-272643 ] Lance commented on JBEHAVE-551: --- I feel that my JBehaveRunner implementation has more similar

[jbehave-dev] [jira] Resolved: (JBEHAVE-550) StoryReporterBuilder does not have an easy way to provide custom StoryReporter(s)

[ https://jira.codehaus.org/browse/JBEHAVE-550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lance resolved JBEHAVE-550. --- Resolution: Won't Fix As suggested by Mauro Talevi, the Format class is sufficient. StoryReporterBuilder does

[jbehave-dev] [jira] Commented: (JBEHAVE-549) StoryReporter forces me to write non thread safe code

[ https://jira.codehaus.org/browse/JBEHAVE-549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=272646#comment-272646 ] Lance commented on JBEHAVE-549: --- This zip file attached to JBEHAVE-551

[jbehave-dev] [jira] Commented: (JBEHAVE-543) Before/After Story/Scenario methods could accept parameters that have meaning at that moment

[ https://jira.codehaus.org/browse/JBEHAVE-543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=272699#comment-272699 ] Adriano Bonat commented on JBEHAVE-543: --- Hey Mauro, thanks for letting me know that I should