Sure, but if JBehave is swallowing and exception and rethrowing as
the vague "Failed to instantiate scenario" then its not helping.
Can this be recoded to throw the raw excpetion.
ClassNotFoundException, NoClassDefFoundException - or some thing else ?
Incidentally, it's the same for JBehave 2.1.1
Regards,
- Paul
On Jan 24, 2009, at 4:49 PM, Mauro Talevi wrote:
Paul Hammant wrote:
What are the circumstances that cause this ?
I have something that works for Mauro, but not for me. Maven is
involved too, FYI
Dude - I think you might need to provide just a tad more context
here :-)
Failure to instantiate a scenario may be due to a number of
circumstances. Typically, it'd be down to incorrect composition of
classpath (e.g. outdated snapshots) or resources not found (e.g. a
container composition script).
I think what you're referring to here is the pico web example
https://svn.codehaus.org/picocontainer/java/2.x/trunk/web/examples/jquery-email/
But there a lot of other "variables" in play - e.g. selenium and
jetty.
Let's pair on this off-line, to find the root cause.
Cheers
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
