On 8/22/07, David Chelimsky <
dchelimsky@...> wrote:
> On 8/22/07, aslak hellesoy <
aslak.hellesoy@...> wrote:
> > On 8/22/07, David Chelimsky <
dchelimsky@...> wrote:
> > > I'd like to ditch rspec's mock framework and let ppl use mocha or
> > > flexmock or RR (or others). RSpec's mocking framework doesn't really
> > > offer anything above those frameworks, and it's therefore an
> > > unnecessary burden to maintain.
> > >
> > > Here's my thinking:
> > >
> > > We break spec/mocks out into a separate project and release the one
> > > and only release when we release rspec 1.1.
> > >
> > > If you want to continue to use rspec mocks you can do so but you'll
> > > have to declare it in spec_helper (or somewhere global), but
> > > spec/mocks will be deprecated, and people would be encouraged to start
> > > using other frameworks.
> > >
> > > This isn't a slam dunk, btw - there are some dependencies on rspec's
> > > mock framework in the rails plugin that would have to be addressed
> > > with either one-off solutions or adapters for the other frameworks.
> > > One thing I do NOT want to do is have RSpec prefer one framework over
> > > another.
> > >
> > > Thoughts?
> >
> > You mean throw away code that we all worked hard to make as good as possible?
> > Sounds good to me. +1 Ja.
> >
> > If we break it out to a separate project, can I recommend we move it
> > to a separate RubyForge project at the same time? Yurii has registered
> > rspec-ext (RSpec Extras), which is currently empty. I've been
> > thinking about moving Spec::Ui and Spec::Distributed there. All these
> > sub projects could share the same svn, but with their own
> > trunk/tags/branches structure. This would allow for separate release
> > cycles. We could put Spec::Mock here.
>
> As long as Yurii is on board that's fine.
>
He is :-)
Aslak
_______________________________________________
rspec-devel mailing list
rspec-devel@...
http://rubyforge.org/mailman/listinfo/rspec-devel