Elizabeth Keogh wrote:
Hi all,
Sorry there's not been much work done on JBehave over the last few
weeks; illness distracted me. The doctor has replaced my immune system
with a new one in pill form so hopefully we can get back on track.
In other words you upgraded from Liz 1.0 to 1.5 :-)
Things I know that still need doing:
- Tidy up of the code base - I'd like to rename the runners and tasks
with a little more consistency. "Run", particularly, I want to get rid
of; I think more people will be interested in JBehave for the stories
than the behaviours anyway.
What's the benefit of removing it? I agree on renaming it, but it can be quite useful to verify a
behaviour given it's class. It acts as a facade to the BehaviourVerifier.
Also, apart from Run, what runners did you have in mind for renaming?
- Ant StoryPrinterTask (should print all stories to a destination dir).
I'd like to add equivalent functionality to maven plugin.
Let's agree on what the plugins/task should provide:
- run behaviours in a Behaviours class (which can consist of many behaviours)
- run story
- print story
- Remove Cotta from the code base
Are we keeping the same functionality of BehavioursLoader, ie to load the behaviours from a marker
class?
Not much, really! Can you think of anything else? I don't know where the
plugins are at the moment...
Maven plugin can do the top two items of list. It currently uses Run to run
behaviours.
So it would have be refactored if that went ...
I'm just going to get on with these in the order above, if no one
objects; please shout if you'd like to take any of them on.
Once we agree on what to do - I have some bandwidth as well now ...
Cheers
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
