[lmcgrath]

I've got two branches up, one with the conditions that cause failure and the one with the fix... Granted, this was all caused by me hacking on the original project and isn't necessarily representative of something most people would encounter.

https://github.com/lmcgrath/arquillian-testrunner-jbehave/tree/cdi-fail

https://github.com/lmcgrath/arquillian-testrunner-jbehave/tree/cdi-pass

Build command:

mvn clean verify -pl core

[kwintesencja]

Hi guys,

firstly congratulations for the work on this extension!

Im using this fork https://github.com/vasilievip/arquillian-testrunner-jbehave with lastest arquillian version(1.1.1) and everything is working fine,

do you have any plan to release an Alpha?

i think its a very important extension to be "hidden" behind github forks as the main project has zero lines of code.

thanks in advance

[kgoedert]

I am also interested in this extension

[kwintesencja]

Hi there, i've attached the maven dependencies of jbehave extension im using, its compiled against arquillian 1.1.1(im using 1.1.2 without problems) and jbehave 3.7. Just unzip it in your maven repository under org\jboss\arquillian folder and declare the maven dependency below:

<dependency>

          <groupId>org.jboss.arquillian.jbehave</groupId>

          <artifactId>arquillian-jbehave-core</artifactId>

          <version>1.0.2</version>

          <scope>test</scope>

</dependency>

i hope that helps

[kwintesencja]

Hi again,

just pushed arquillian-jbehave to a private repo:

<repository>

            <id>arquillian jbehave UNofficial maven repo</id>

            <url>http://arquillian-jbehave-repo.googlecode.com/git/</url>

            <layout>default</layout>

</repository>

dependency is the same:

<dependency>

          <groupId>org.jboss.arquillian.jbehave</groupId>

          <artifactId>arquillian-jbehave-core</artifactId>

          <version>1.0.2</version>

          <scope>test</scope>

       <!-- you can excluse embbeded jbehave version(3.7) and add a newer one-->

</dependency>