Hi all,

I've come around a strange behaviour. I'm on that issue since 5 days. Now
I've understood the problem.

When I run jebahave-maven-plugin on a single module project the
InjectableEmbedder can find my stories.

When I run jebahave-maven-plugin on a muti module project, from the project
defining stories the InjectableEmbedder can find my stories.

When I run jebahave-maven-plugin on a muti module project, from the root
project the InjectableEmbedder can't find my stories. I guess it's related
to how I look for the stories :

    /**
     * @see org.jbehave.core.Embeddable#run()
     */
    @Test
    @Override
    public void run() throws Throwable {
        injectedEmbedder().runStoriesAsPaths(storyPaths());
    }

    protected List<String> storyPaths() {
        return new StoryFinder().findPaths("src/test/resources",
Arrays.asList("**/*.story"), null);
    }

my dirs are organized this way :

 - root
   + acceptance-tests
   + server
   + webapp

When I run mvn clean install -Pjbehave from root nothing happens because
root project, which has pom packaging doesn't have any src/test/resources
dir.
When I run mvn clean install -Pjbehave from acceptance-tests it runs the
sories.

My build always runs on the root dir. I don't want to merge all modules just
because of jbehave. Any idea how I could keep the best of both worlds ?

Thx

Reply via email to