Ravi Varanasi wrote:
Mauro -
Below are the answers -
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?
Running the scenarios from command line through Maven works, but running inside
hudson causes the Class loader issues.
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.
The web runner was included to have the capability of running the scenarios from
a browser (however have to get past this issue)
I do have a workaround - instead of running the mvn clean run-integration-test
from a hudson build plan, wrote a batch file that runs mvn clean
run-integration-test. That seems to work.
Uhm ... OTOH, it seems more of an issue with Hudson's classloading.
Have you tried any other CI server? E.g. could you download and try out
TeamCity or another commercial tools (they are fully functional by free
for limited users).
Other thing I would suggest is if you could reproduce problem in a
bare-bone Maven project, you could attach it as test case to a Jira
issue, which we can use for investigation.
I would suggest that you send it to the Hudson as well, asking them why
it would work in a batch file only.
Cheers
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
