Ravi Varanasi wrote:
Mauro -
Though the exception is thrown only when the run-scenarios is run (bound to
integration-test phase). If the scenarios are not run the test works fine.
Below is the output from dependency tree
[INFO] +- org.springframework:spring-core:jar:2.5.6:compile
[INFO] | \- commons-logging:commons-logging:jar:1.1.1:compile
[INFO] +- org.springframework:spring-beans:jar:2.5.6:compile
[INFO] +- org.springframework:spring-context:jar:2.5.6:compile
[INFO] | \- aopalliance:aopalliance:jar:1.0:compile
[INFO] +- org.springframework:spring-tx:jar:2.5.6:compile
[INFO] +- org.springframework:spring-orm:jar:2.5.6:compile
[INFO] +- org.springframework:spring-jdbc:jar:2.5.6:compile
[INFO] +- org.springframework:spring-aop:jar:2.5.6:compile
[INFO] +- junit:junit:jar:4.4:test
[INFO] +- org.hamcrest:hamcrest-all:jar:1.1:test
[INFO] +- org.jbehave:jbehave-core:jar:2.3:compile
[INFO] | \- junit:junit-dep:jar:4.5:compile
[INFO] +- org.jbehave.web:jbehave-web:pom:2.1.4:compile
[INFO] +- org.jbehave.web:jbehave-web-runner:jar:2.1.4:compile
[INFO] | +- org.jbehave.web:jbehave-web-io:jar:2.1.4:compile
[INFO] | | +- commons-lang:commons-lang:jar:2.3:compile
[INFO] | | +- commons-fileupload:commons-fileupload:jar:1.2:compile
[INFO] | | \- org.apache.commons:commons-compress:jar:1.0:compile
[INFO] | +- org.codehaus.waffle:waffle-core:jar:1.3:compile
[INFO] | | +- ognl:ognl:jar:2.7.3:compile
[INFO] | | | \- jboss:javassist:jar:3.7.ga:compile
[INFO] | | \- org.picocontainer:picocontainer:jar:2.5.1:compile
[INFO] | +- org.freemarker:freemarker:jar:2.3.13:compile
[INFO] | +- opensymphony:sitemesh:jar:2.3:compile
[INFO] | +- javax.servlet:jstl:jar:1.1.2:compile
[INFO] | \- taglibs:standard:jar:1.1.2:compile
[INFO] +- org.jbehave.web:jbehave-web-selenium:jar:2.1.4:compile
[INFO] |\-org.seleniumhq.selenium.client-drivers:selenium-java-client-driver:jar
:1.0.1:compile
I did not see multiple versions of JCL or log4j.
The classloader that is passed to the scenario. The scenarios run fine when
running maven from command line, but does not work inside of hudson
Is there an issue since hudson passes the it's classloader?
Thanks for the earlier responses.
Hi Ravi,
let's take in steps:
1. Can you run scenarios successfully using Maven in CLI on your local
machine - but not embedded in Hudson or any other CI?
2. Are you running in CLI or via web runner? I see you have in your
dependency tree the jbehave-web-runner and I'm not sure what you use it
for.
Cheers
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
