[jbehave-dev] Re: DI with Picocontainer...

2010-01-07 Thread Mauro Talevi
Cristiano Gavião wrote: Hi, Humm, ok. I already tried some experimental work myself with guice and jbehave, mostly unsucessfull until now... But I could get guice to work together with junit, but it was needed to create an expecific extension of BlockJUnit4ClassRunner.. Btw, I really th

Re: [jbehave-dev] Re: DI with Picocontainer...

2010-01-07 Thread Paul Hammant
Look at TraderSteps, and where you see the StepsFactory in use, imagine using PicoStepsFactory or GuiceStepsFactory instead. Its not meant to be an abstraction as its end-user code. What it means is that Guice will be able to fill constructors for Steps POJOs. Not sure about scopes, JB seems

[jbehave-scm] [1503] trunk/core/jbehave-core/src/main/java/org/jbehave/scenario/steps: JBEHAVE-231: Refactored StepsFactory to not use static methods and to provide configuration via constructor.

2010-01-07 Thread mauro
Title: [1503] trunk/core/jbehave-core/src/main/java/org/jbehave/scenario/steps: JBEHAVE-231: Refactored StepsFactory to not use static methods and to provide configuration via constructor. Revision 1503 Author mauro Date 2010-01-07 11:10:31 -0600 (Thu, 07 Jan 2010) Log Message JBEHAVE-23

Re: [jbehave-dev] Re: DI with Picocontainer...

2010-01-07 Thread Cristiano Gavião
Hi Paul, Im looking for those changes right now... I are right, do not have to extends Steps and to allow addSteps out of constructor will help a lot... nice job !! Paul Hammant escreveu: It is not going to make it to 2.4, no. Though some of teh refactorings we're doing in 2.4 will faci

[jbehave-scm] [1502] trunk/core/jbehave-core/src/main/java/org/jbehave/scenario/steps: JBEHAVE-231: Refactored Steps class to have a single instance member, either itself or the injected steps insta

2010-01-07 Thread mauro
Title: [1502] trunk/core/jbehave-core/src/main/java/org/jbehave/scenario/steps: JBEHAVE-231: Refactored Steps class to have a single instance member, either itself or the injected steps instance. Revision 1502 Author mauro Date 2010-01-07 10:52:37 -0600 (Thu, 07 Jan 2010) Log Message JBE

[jbehave-dev] [jira] Created: (JBEHAVE-231) Allow CandidateSteps methods to be defined in POJOs

2010-01-07 Thread Mauro Talevi (JIRA)
Allow CandidateSteps methods to be defined in POJOs --- Key: JBEHAVE-231 URL: http://jira.codehaus.org/browse/JBEHAVE-231 Project: JBehave Issue Type: Improvement Components: Core

Re: [jbehave-dev] Re: DI with Picocontainer...

2010-01-07 Thread Paul Hammant
It is not going to make it to 2.4, no. Though some of teh refactorings we're doing in 2.4 will facilitate. One that Mauro's completing now is making steps implementation classes POJOs. I.e. they don't have to extend Steps anymore. The Guice one should be pretty similar. Regards, - Paul On

Re: [jbehave-dev] Re: DI with Picocontainer...

2010-01-07 Thread Cristiano Gavião
Hi, Humm, ok. I already tried some experimental work myself with guice and jbehave, mostly unsucessfull until now... But I could get guice to work together with junit, but it was needed to create an expecific extension of BlockJUnit4ClassRunner.. Btw, I really think that is should be pos

[jbehave-scm] [1501] trunk/core/jbehave-core/src/main/java/org/jbehave/scenario/steps: POJO steps implementation done; backwards compatible

2010-01-07 Thread paul
Title: [1501] trunk/core/jbehave-core/src/main/java/org/jbehave/scenario/steps: POJO steps implementation done; backwards compatible Revision 1501 Author paul Date 2010-01-07 09:55:35 -0600 (Thu, 07 Jan 2010) Log Message POJO steps implementation done; backwards compatible Modified Paths

[jbehave-dev] [jira] Updated: (JBEHAVE-216) Allow to indicate which is the weight of each StepsCandidate class used by a Scenario class to resolve duplicated methods.

2010-01-07 Thread Mauro Talevi (JIRA)
[ http://jira.codehaus.org/browse/JBEHAVE-216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-216: - Fix Version/s: (was: 2.4) 2.5 > Allow to indicate which is the weight of each S

[jbehave-dev] [jira] Updated: (JBEHAVE-207) Exclude SCM patterns from ScenarioClassNameFinder

2010-01-07 Thread Mauro Talevi (JIRA)
[ http://jira.codehaus.org/browse/JBEHAVE-207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-207: - Component/s: Core Affects Version/s: 2.3 Fix Version/s: (was: 2.4)

[jbehave-dev] [jira] Updated: (JBEHAVE-163) Support comments in plain-text scenarios

2010-01-07 Thread Mauro Talevi (JIRA)
[ http://jira.codehaus.org/browse/JBEHAVE-163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-163: - Fix Version/s: (was: 2.4) 2.5 > Support comments in plain-text scenarios >

[jbehave-dev] [jira] Updated: (JBEHAVE-206) Regex overflow in using Examples table

2010-01-07 Thread Mauro Talevi (JIRA)
[ http://jira.codehaus.org/browse/JBEHAVE-206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-206: - Fix Version/s: (was: 2.4) 2.5 > Regex overflow in using Examples table > --

[jbehave-dev] Re: Report directory creation issue on wndows xp

2010-01-07 Thread Mauro Talevi
Shouldn't Windows understand URL encoding of spaces? I'll look into it a bit more. Cheers Cristiano Gavião wrote: Hi, Trying to run som example of jbehave with reports and jbehave is creating another file structure. I've run using junit inside eclipse on windows xp. The folders created by

[jbehave-dev] Re: Is there a way to inject the entire row as exampleTable?

2010-01-07 Thread Mauro Talevi
Cristiano Gavião wrote: Hummm... ok Cold you give some clue or an example how could I inject the whole table on a method? I've tried to create ExamplesTableConverter but doesnt works so I could create a converter that allowed me to put a separated by comma array list inside some Exampl

[jbehave-dev] Re: DI with Picocontainer...

2010-01-07 Thread Mauro Talevi
Cristiano, the DI support is still very much experimental work we're doing with Paul. We're still trying to work out some fundamentals and if it's stable enough to release in 2.4, or need to postpone it to 2.5 (hence we've not gone "public" with it). As soon as we've got a stable build wit