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 Jan 7, 2010, at 10:45 AM, 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 think that is should be postponed to 2.5. There is already a > lot of new features to deal with on 2.4 :-) > > regards > > Mauro Talevi escreveu: >> 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 with examples we'll >> post the details and update the documentation. >> >> The issue related to this is JBEHAVE-133. We are currently working on Pico >> support, with other containers to follow suit. >> >> Cheers >> >> Cristiano Gavião wrote: >>> Hi people... >>> >>> I got glad to see that was commited some work for a new extension with a DI >>> container... very nice... >>> >>> I've got interested in knowing little more about this feature... >>> >>> What are the plans and desired behaviors for DI extension for jBehave. What >>> are the goals for this feature? >>> >>> Which classes would be enabled for being injected on jbehave context? Steps >>> on Scenarios? Configuration Classes in both steps and scenarios? Third lib >>> classes? >>> >>> And about configuring DI: using xml, properties or annotation? >>> >>> is there a issue for this on jira? >>> >>> thanks >>> >>> Cristiano >>> >>> --------------------------------------------------------------------- >>> To unsubscribe from this list, please visit: >>> >>> http://xircles.codehaus.org/manage_email >>> >>> >>> >> >> >> --------------------------------------------------------------------- >> To unsubscribe from this list, please visit: >> >> http://xircles.codehaus.org/manage_email >> >> > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
