I can't work this out. While making a custom version of JBehave to
further debug the issue, it disappeared.
I'm now at a place where all steps are marked pending though, and I
can't see why.
Regards,
- Paul
On Jan 25, 2009, at 2:51 AM, Mauro Talevi wrote:
Paul Hammant wrote:
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 ?
If you run Maven with stacktraces on (mvn -e) it will give you the
root exception. It's not swallowing it, it's simply wrapping it to
express the failure point and the scenario it fails on. The root is
in the stacktrace.
Incidentally, it's the same for JBehave 2.1.1
Yes - I was just about to write comment on this.
This was a regression I introduced in 2.1 as I normally use compile
scope and did not have a behaviour example for test scope: now we do
have it :-)
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
