Re: [jbehave-dev] Re: [jbehave-scm] [jbehave] [612] trunk/core/src/java/jbehave/core: [dn] replaced constraint with matcher throughout (except in JMockSugar because I can't)

2006-12-05 Thread Shane Duan
Ah. Thanks for the explanation. Are we going to add it now? In this way, people who are using Java5 can use this style right now. On 12/5/06, Dan North [EMAIL PROTECTED] wrote: That's what I meant - sorry, didn't explain it very well. In Ensure we will have pairs of methods, called

[jbehave-scm] [jbehave] [613] trunk: Removed redundant method in Scenario - already in super interface HasCleanUp.

2006-12-05 Thread mauro
Title: [jbehave] [613] trunk: Removed redundant method in Scenario - already in super interface HasCleanUp. Revision 613 Author mauro Date 2006-12-05 06:30:33 -0600 (Tue, 05 Dec 2006) Log Message Removed redundant method in Scenario - already in super interface HasCleanUp. Modified Paths

[jbehave-scm] [jbehave] [614] trunk/core/src/java/jbehave/core/story/domain: Removed Scenarios - merged functionality in ScenarioDrivenStory.

2006-12-05 Thread mauro
Title: [jbehave] [614] trunk/core/src/java/jbehave/core/story/domain: Removed Scenarios - merged functionality in ScenarioDrivenStory. Revision 614 Author mauro Date 2006-12-05 07:05:03 -0600 (Tue, 05 Dec 2006) Log Message Removed Scenarios - merged functionality in ScenarioDrivenStory.

Re: [jbehave-dev] simplicating scenarios

2006-12-05 Thread Mauro Talevi
Joe Walnes wrote: Just to clarify - is the scope of assemble() to avoid big constructors or is there another usecase for it? That's definitely one of the reasons. Another is to allow the API to evolve over time without necessarily breaking people's code when a new dependency is