[
http://jira.codehaus.org/browse/JBEHAVE-233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=226921#action_226921
]
Tim Moore commented on JBEHAVE-233:
-----------------------------------
I totally agree with this.
We've written a partial xtext grammar which gives us fairly trivially an editor
with syntax highlighting and formatting. I was hoping to offer it when it was a
bit more mature.
xtext seems like a good framework to build extra validation of story files on
top of, auto-completion, etc;
but it seems hard in terms of candidate step discovery (look for references
from Class associated with story file? Were the step classes actually added?
Did another class add them somehow?). Likewise in the other direction.
> 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
> 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 contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.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
