[
http://jira.codehaus.org/browse/JBEHAVE-394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=246177#action_246177
]
Mauro Talevi commented on JBEHAVE-394:
--
Hi Alan, if you are happy to contribute the plugin the
[
http://jira.codehaus.org/browse/JBEHAVE-401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mauro Talevi resolved JBEHAVE-401.
--
Resolution: Duplicate
Duplicate of JBEHAVE-397.
> XML Scenario reporter doesn't always include a cl
[
http://jira.codehaus.org/browse/JBEHAVE-397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mauro Talevi resolved JBEHAVE-397.
--
Resolution: Fixed
Patch applied.
> Failure to execute all scenarios within a story.
> -
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "jbehave-core".
The branch, master has been updated
via 7e13bdf929ca49cf18901669e2d5726bed7fe95e (commit)
from 1501bb0cfaf2587
[
http://jira.codehaus.org/browse/JBEHAVE-401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mauro Talevi updated JBEHAVE-401:
-
Fix Version/s: 3.2
> XML Scenario reporter doesn't always include a closing story xml tag
> --
[
http://jira.codehaus.org/browse/JBEHAVE-397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mauro Talevi updated JBEHAVE-397:
-
Component/s: Core
Fix Version/s: 3.2
> Failure to execute all scenarios within a story.
> --