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,
Ant-run scenarios also require a constructor with ClassLoader parameter.
The docs should say that only core-run scenarios (i.e. run via IDE) do
not. I'll update it.
Note that I've now refactored the ScenarioClassLoader to instantiate
scenarios via multiple constructors:
http://jira.codehaus.org/browse/JBEHAVE-199
But this does not change things when running with Ant, the classloader
need to be specified with the content of the classpath constructed by
Ant task. Unless one uses some other way to specify the classloader.
I'm happy to explore different ways of doing this to support multiple
ways of operation. But at the moment, having the ClassLoader
constructor is the recommended and support way to run via CLI, both via
Ant and Maven.
Cheers
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
