Hi, I was getting a little peeved by eclipse not showing the individual stories in it's JUnit results view when running JBehave, so I implemented a new runner for use with @RunWith that does. It works slightly differently to the existing JUnit integration, there's no need for a @Test method any more and the stories are selected using an annotation. But it provides useful feedback, I think, to how story execution is progressing and quickly highlights which stories failed.
It's all sitting in the new-junit-runner branch on my github fork. I added a WithGuiceJBehaveRunner sample in the jbehave-trader-guice-example module to show it works. It's a bit embryonic at the moment, you can break it if some of the @UsingEmbedder flags are wrong for instance, if you execute it using eCobertura for coverage the reports get written into workspace\.metadata\somewhere\else\ and some other bits and pieces. Also, I had to write a new Maven Mojo to use the @StoryPaths annotation so that the XyzStories class worked from both maven and eclipse. However, I think it's easier to use than the current maven plugin, which had left me scratching my head for a good couple of hours when first trying to use it. What are the chances of including this, or something like it, in the main JBehave distro. If this is never going to happen, I'll have to package it up as a separate jar, but I'd rather not. Obviously I'll need to finish it, and fix all the edge cases first :) Thanks, Dan.
