Ooh! I like the idea of leaving Scenario as the default abstract class, under JUnitScenario (so effectively it's just an alias for it).
2008/9/24 Mauro Talevi <[EMAIL PROTECTED]> > Mauro Talevi wrote: > > Apart from the rename of Scenario - I had already gone through this >> process (see previous email I sent, in which I posed the issue of the >> backward compat). >> >> So, seeing that backward compat is deemed more important (and I do not >> disagree) I've now renamed Scenario interface to RunnableScenario and >> reinstated Scenario as deprecated abstract class extending >> JUnitScenario. We can then remove Scenario at a later stage, or >> perhaps we could simply remove deprecation and leave Scenario to be the >> default abstract class. >> > > I've deployed latest snapshot and verified that it's completely backward > compatible with 2.0.x > > > Cheers > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > >
