Robison,
Also, if you are using an IoC container (pico, guice, spring, weld), then you can get your steps from the container and they can live whereever. The spring-security example has that. Just another thought... Brian ----- Original message ----- From: "Robison Santos" <[email protected]> To: [email protected] Date: Mon, 19 Sep 2011 09:15:45 -0300 Subject: Re: [jbehave-user] Using story paths different from JUnitStory path Good, I'll try that. Do you have any code example I can base myself on? If not, that's not a problem. Thanks again, Robison On Sun, Sep 18, 2011 at 9:06 PM, Mauro Talevi <[1][email protected]> wrote: By default, the .story files are looked up in the same package as the the Story* classes. If you want a different behaviour, you can implement your own StoryPathResolver and configure it in the Configuration. Cheers On 19/09/2011 02:01, Robison Santos wrote: Hi, I'm new here and I wonder how can I write a "JBehave project" with a structure like this: -src - com - jbehave - mystories - story1.story - story2.story - mysteps - Story1Steps.java - Story2Steps.java - myconfig - Story1.java - Story2.java Having, Story1.java and Story2.java subclasses of JUnitStory. I'm trying, without success, to set those classes to find their specific stories in the path /com/jbehave/mystories, and I'm now out of ideas. Is there a way to do that? Thanks, -- Robison W R Santos -------------------------------------------------------------- ------- To unsubscribe from this list, please visit: [2]http://xircles.codehaus.org/manage_email -- Robison W R Santos Bach. Ciências da Computação "NUNCA generalise. Generalisar é SEMPRE um erro." References 1. mailto:[email protected] 2. http://xircles.codehaus.org/manage_email --- Brian Repko LearnThinkCode, Inc. http://www.learnthinkcode.com email: [email protected] phone: +1 612 229 6779
