[ https://jira.codehaus.org/browse/JBEHAVE-233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=289168#comment-289168 ]
Arnauld Loyer commented on JBEHAVE-233: --------------------------------------- > It was not able to get to work properly, i.e. configure the steps classes > which are not found. can you provide more information about your issue. > the scan approach may work for POJO classes with default constructors Actually no, it is based on eclipse representation of java file or class file. ".java" and ".class" (for classes into jar file) are read into JDT internal representation and allows to scan for the presence of annotations. > but now for steps classes created by other means, e.g. a CI container. right, it is not supported. Even if the Embedder is leverage, it still requires configuration that may not be available in a "passive" project which does not load any configuration, or setup environment. It would require to plug into a "live" environment to retrieve the step definitions. > 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