[
https://jira.codehaus.org/browse/JBEHAVE-543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=274758#comment-274758
]
Adriano Bonat commented on JBEHAVE-543:
---------------------------------------
Hey Mauro,
I've checked in some examples using this feature and after some thought I
didn't see a reason to report the execution of the parametrized before/after
annotations, so I've removed the TODO.
About the refactoring in StepCreator, the idea is delegate the method
invocation in the ParametrisedStep to the MethodInvoker that this task
introduced. I've started this yesterday but still need to see how can I keep
the current reporting calls working as they do currently.
Sorry for the delayed reply :)
> Before/After Story/Scenario methods could accept parameters that have meaning
> at that moment
> --------------------------------------------------------------------------------------------
>
> Key: JBEHAVE-543
> URL: https://jira.codehaus.org/browse/JBEHAVE-543
> Project: JBehave
> Issue Type: New Feature
> Components: Core
> Reporter: Paul Hammant
> Assignee: Mauro Talevi
> Fix For: 3.5
>
>
> For example -
> bq. public void myBeforeStory(@Named("someMetaTag") String someMetaTag) { .. }
> This would be a poor-mans version of JBEHAVE-541
--
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
