Ben Sullivan wrote:
Hi Mauro
Great thanks for that.
I tried the new binary today. My Scenario classes are being found now
but it seems that there is a dependency on having constructor signatures
that include a ClassLoader parameter. Without this I get the stack
trace shown below in my build output...
My understanding was that the ClassLoader parameter was only necessary
when using Maven. I'm just using plain old Ant in this case.
With ClassLoaders in the constructor signatures of my Scenario,
Configuration and Step implementations, all seems to run smoothly.
I'm assuming the current doco is correct (Ant does not require
ClassLoader param) and this is an issue? Let me know if you want me to
send through the IntelliJ project for you to reproduce locally.
Many thanks for your prompt replies on this stuff.
Ben,
I've made the class loader injection configurable:
http://jira.codehaus.org/browse/JBEHAVE-202
The examples - both Ant and Maven - have been updated to use it when
strictly necessary (i.e. when loading i18n resource bundles).
I've deployed a snapshot and will test it tomorrow before cutting 2.3.2
release.
Please give it whirl as well if you get a chance.
Cheers
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
