I'm not quite sure I understand what you mean by the comment in http://jira.codehaus.org/browse/JBEHAVE-126? For my request, see http://jira.codehaus.org/browse/JBEHAVE-153
Also; what is the reason for using Blur On Tue, Dec 9, 2008 at 12:28 AM, Mauro Talevi <[EMAIL PROTECTED]>wrote: > Hi Egil, > > Egil Østhus wrote: > > Tempting :) >> > > You can resist everything but temptation (O. Wilde) :-) > > > In my story/scenario files, I can't find any way to define the pri. of >> each scenario. Is there any way to do this? I guess this should be a part of >> the org.jbehave.scenario.definition.ScenarioDefinition? This could then be >> used for different outputs as discussed in previous mails. What do you guys >> think? Does this make any sense? >> >> > Yes - it's a feature I've started to feel the need for in my projects too - > to build scenarios on previous scenario. I'm in two minds as whether the > priority/ordering use case could not be better served via the GivenScenario > feature > (http://jira.codehaus.org/browse/JBEHAVE-126), which I've now started work > on. The advantage being IMO that we'd keep each scenario "independent" of > others - and any pre-requisites would be declared by the scenario/story > itself (useful mostly when running in IDE). Of course, the two use cases > are not incompatible and I think it would be a useful addition to have an > ordering feature. > > Why don't you open a new Jira issue detailing your use case? > > > Cheers > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > -- See my pictures at http://www.flickr.com/photos/[EMAIL PROTECTED]/ free code-giveaways at http://codeisland.blogspot.com/
