[jbehave-dev] [jira] Commented: (JBEHAVE-232) Replace @Named variable annotation by pattern matching of variable names used in step annotation

[ http://jira.codehaus.org/browse/JBEHAVE-232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=225997#action_225997 ] Jonathan Ross commented on JBEHAVE-232: --- Hi Paul. Sorry if my examples weren't clear enough.

[jbehave-dev] [jira] Commented: (JBEHAVE-163) Support comments in plain-text scenarios

[ http://jira.codehaus.org/browse/JBEHAVE-163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=206973#action_206973 ] Jonathan Ross commented on JBEHAVE-163: --- Unfortunately, if the step preceding the comment ends

[jbehave-dev] [jira] Commented: (JBEHAVE-216) Allow to indicate which is the weight of each StepsCandidate class used by a Scenario class to resolve duplicated methods.

[ http://jira.codehaus.org/browse/JBEHAVE-216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=206974#action_206974 ] Jonathan Ross commented on JBEHAVE-216: --- A similar issue comes into play if you have similarly

[jbehave-dev] [jira] Created: (JBEHAVE-232) Replace @Named variable annotation by pattern matching of variable names used in step annotation

Replace @Named variable annotation by pattern matching of variable names used in step annotation Key: JBEHAVE-232 URL: http://jira.codehaus.org/browse/JBEHAVE-232

[jbehave-dev] [jira] Created: (JBEHAVE-233) Eclipse plugin for navigating between textual and code steps

Eclipse plugin for navigating between textual and code steps Key: JBEHAVE-233 URL: http://jira.codehaus.org/browse/JBEHAVE-233 Project: JBehave Issue Type: New Feature

[jbehave-dev] [jira] Created: (JBEHAVE-234) Improve JUnit integration

Improve JUnit integration - Key: JBEHAVE-234 URL: http://jira.codehaus.org/browse/JBEHAVE-234 Project: JBehave Issue Type: Improvement Reporter: Jonathan Ross As a developer using jBehave running in