Hi Shane,
I've reverted your change, which contains generics. Maybe when we make the move to using Java 5 we can revisit this, but it won't be until JBehave 2.0. I would also like to keep Cotta out of the codebase, please.
There is a different solution! I have always intended to make the Ant build use Ant's scanner to find all the behaviours, and only verify the Ant task behaviours separately. This is a great spur for me to do that, this weekend. It already works (see the Hellbound behaviours); just need to get on and do it. This approach has scaled on every JUnit project I've been on, and allows coolness like forking the vm.
Apologies for not being involved in the discussion earlier, and thanks for calling it in.
Mauro, is there anything similar for Maven? If so, we can remove the AllBehaviours completely.
Cheers,
Liz.
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
I've reverted your change, which contains generics. Maybe when we make the move to using Java 5 we can revisit this, but it won't be until JBehave 2.0. I would also like to keep Cotta out of the codebase, please.
There is a different solution! I have always intended to make the Ant build use Ant's scanner to find all the behaviours, and only verify the Ant task behaviours separately. This is a great spur for me to do that, this weekend. It already works (see the Hellbound behaviours); just need to get on and do it. This approach has scaled on every JUnit project I've been on, and allows coolness like forking the vm.
Apologies for not being involved in the discussion earlier, and thanks for calling it in.
Mauro, is there anything similar for Maven? If so, we can remove the AllBehaviours completely.
Cheers,
Liz.
