[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] 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-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] 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: https://jira.

[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] 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-tabpanel&focusedCommentId=272629#comment-272629 ] Mauro Talevi commented on JBEHAVE-543: -- Adriano, I pulled your commits (except the one above)

[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: - Fix Version/s: 3.5 Assignee: Mauro Talevi > Before/After Story/Scenario methods could accept

[jbehave-dev] [jira] Commented: (JBEHAVE-548) @BeforeExample und @AfterExample

[ https://jira.codehaus.org/browse/JBEHAVE-548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=272575#comment-272575 ] Lance commented on JBEHAVE-548: --- You can use the JUnitTestRunner that I have attached to jira JBEHAV

[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 ] Lance updated JBEHAVE-551: -- Attachment: jbehave-improved-junit-runner.zip I have updated the code which includes the following: Maven pom JBeha