[
https://jira.codehaus.org/browse/JBEHAVE-233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=293738#comment-293738
]
Arnauld Loyer commented on JBEHAVE-233:
---------------------------------------
Sorry for the late response, i strongly think your only issue is due to the
default filtered classes in `Preferences > JBehave > Class Scanner`
make sure to remove the exclude filter `org.jbehave.*` if your sample classes
are part of `org.jbehave` package.
> Eclipse plugin for navigating between textual and code steps
> ------------------------------------------------------------
>
> Key: JBEHAVE-233
> URL: https://jira.codehaus.org/browse/JBEHAVE-233
> Project: JBehave
> Issue Type: New Feature
> Reporter: Jonathan Ross
>
> As an avid user of jBehave, I find maintaining steps very laborious, so I
> would like an eclipse plugin with:
> * support for opening declarations of steps from the scenario files
> * support for finding usages of steps in scenario files from the declaration
> * support for opening the declaration of failed steps when running junit
> Nice to have:
> * refactoring support: when editing the annotations, scenarios using the step
> get rewritten
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
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
