Dan North wrote:
Ooh! I like the idea of leaving Scenario as the default abstract class, under JUnitScenario (so effectively it's just an alias for it).
Ok - so you're saying we should un-deprecate it as leave it as a default alias?
Not against an alias class, but perhaps I would name that alias DefaultScenario (identical to what is now Scenario) - and leave Scenario deprecated for 2.1+ (with the idea of eventually removing it).
The main reason is that it's kinda odd to have a SomethingScenario be implemented by Scenario - the convention goes the other way.
WDYT? --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
