David James
2007-Jun-08 03:08 UTC
[rspec-users] Still recommend the plugins over the gems?
> We strongly recommend you install RSpec and Spec::Rails as plugins > (as opposed to relying on an RSpec gem). See special instructions > below if you want to install the HEAD of the trunk, or an older > version.(from http://rspec.rubyforge.org/documentation/rails/install.html) Is this still the case? Why? Is the rspec_on_rails available in gem form? Does rspec_generator (the gem, currently at 0.5.15) correspond to the plugins? -David
Scott Taylor
2007-Jun-08 06:01 UTC
[rspec-users] Still recommend the plugins over the gems?
On Jun 7, 2007, at 11:08 PM, David James wrote:>> We strongly recommend you install RSpec and Spec::Rails as plugins >> (as opposed to relying on an RSpec gem). See special instructions >> below if you want to install the HEAD of the trunk, or an older >> version. > (from http://rspec.rubyforge.org/documentation/rails/install.html) > > Is this still the case? Why? > > Is the rspec_on_rails available in gem form?The rspec_on_rails plugin has never been available in gem form, has it? Potentially, you could install the rspec_on_rails plugin, while using the autotest gem (assuming you got the version numbers exactly right). Or am I wrong on this one, as well? Scott
David Chelimsky
2007-Jun-08 12:42 UTC
[rspec-users] Still recommend the plugins over the gems?
On 6/8/07, Scott Taylor <mailing_lists at railsnewbie.com> wrote:> > On Jun 7, 2007, at 11:08 PM, David James wrote: > > >> We strongly recommend you install RSpec and Spec::Rails as plugins > >> (as opposed to relying on an RSpec gem). See special instructions > >> below if you want to install the HEAD of the trunk, or an older > >> version. > > (from http://rspec.rubyforge.org/documentation/rails/install.html) > > > > Is this still the case? Why? > > > > Is the rspec_on_rails available in gem form? > > The rspec_on_rails plugin has never been available in gem form, has it? > > Potentially, you could install the rspec_on_rails plugin, while using > the autotest gem (assuming you got the version numbers exactly > right). Or am I wrong on this one, as well?autotest? I think he was just asking about rspec and rspec_on_rails. The rspec_generator is ancient. I''d delete it. We started off w/ gems but decided w/ all the volatility it was easier to manage different versions directly in the app as plugins. As things are less volatile now, we could revisit this.> > Scott > > _______________________________________________ > rspec-users mailing list > rspec-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/rspec-users >
Brandon Keepers
2007-Jun-08 12:52 UTC
[rspec-users] Still recommend the plugins over the gems?
On Jun 8, 2007, at 8:42 AM, David Chelimsky wrote:> We started off w/ gems but decided w/ all the volatility it was easier > to manage different versions directly in the app as plugins. As things > are less volatile now, we could revisit this.Think it would be possible to make the plugin not depend on a specific version of rspec, but maybe just a branch (e.g. 1.0.x)? Brandon
David Chelimsky
2007-Jun-08 13:19 UTC
[rspec-users] Still recommend the plugins over the gems?
On 6/8/07, Brandon Keepers <bkeepers at gmail.com> wrote:> > On Jun 8, 2007, at 8:42 AM, David Chelimsky wrote: > > > We started off w/ gems but decided w/ all the volatility it was easier > > to manage different versions directly in the app as plugins. As things > > are less volatile now, we could revisit this. > > Think it would be possible to make the plugin not depend on a > specific version of rspec, but maybe just a branch (e.g. 1.0.x)?I''m not sure we''re there yet. With 1.0, we committed to reducing volatility in the public API. rspec_on_rails, however, is an extension of rspec and most of the extension points are not published extension points. We''re basically subclassing specific classes in RSpec. If the structure changes, which it might if we decide there''s value in it, we''re going to have to mirror those changes in rspec_on_rails. We''ve started to provide extension APIs like using Spec::Runner.configure instead of forcing you to monkey patch rspec to include modules in the examples, etc. But we have a long way to go before I''d be comfortable decoupling rspec_on_rails from rspec in this way. David> > Brandon > _______________________________________________ > rspec-users mailing list > rspec-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/rspec-users >