[rspec-devel] [ rspec-Feature Requests-6898 ] Can we separate rspec from the plugins?

noreply at rubyforge.org noreply at rubyforge.org
Sun Nov 26 20:18:05 EST 2006


Feature Requests item #6898, was opened at 2006-11-26 18:49
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=3152&aid=6898&group_id=797

Category: None
Group: None
Status: Open
Priority: 3
Submitted By: Pat Maddox (pergesu)
Assigned to: Nobody (None)
Summary: Can we separate rspec from the plugins?

Initial Comment:
I'm trying to use rspec to do my rails development, and a while ago I had found a way to be able to use edge rspec and the plugin.  Today I svn uped and to my surprise, the rspec code (not the plugin) ended up downloading three different versions of Rails.

Is there any way we can separate the rspec code base from the plugins?  If I download trunk, I just want it to be rspec itself...the Rails stuff shouldn't be under it.  If I'm in a Rails project, I can install the rspec libs as a plugin, and the Rails plugin separately.  Some of you may have seen my article a couple weeks ago about doing that (site is no longer up, sorry).

Basically now it's a real pain to try to use edge rspec inside a Rails project.  However that's the best way to make updates both to rspec itself and the plugin.  If you could make it so they're separated more cleanly, I'd happily bang out Rails related bugs and RFEs as I work on my own Rails apps.

----------------------------------------------------------------------

>Comment By: Aslak Hellesøy (aslak_hellesoy)
Date: 2006-11-26 20:18

Message:
Ok, I can drive it. I'll probably do it on a branch. Does anyone know if svn handles a merge back to trunk when files have been moved on the branch and modified on the trunk in the meanwhile?

----------------------------------------------------------------------

Comment By: David Chelimsky (dchelimsky)
Date: 2006-11-26 20:03

Message:
One thing about separating rspec_on_rails and rspec_on_rails_demo. Right now, the specs inside rspec_on_rails won't work w/o the demo in place (because the demo also houses files specifically present for the specs). So, initially, we'd run the specs via the demo, but eventually we want to make the rspec_on_rails tree be complete (i.e. you can run all the specs within that tree).

Make sense?

Otherwise, this sounds good. I think we should plan a time to do this. Aslak - do you want to drive it?

Thanks,
David

----------------------------------------------------------------------

Comment By: Pat Maddox (pergesu)
Date: 2006-11-26 19:56

Message:
On top of svn mv and rake hacking, you'll have to edit all
the files that "require 'some_other_file'" to use relative
paths.  When I was splitting stuff out on my own that's what
I had to do...but it's not too bad.

The proposed structure is basically exactly what I'd like to
see.  Makes it really easy to include just what you want,
which of course makes it easy to make changes.

----------------------------------------------------------------------

Comment By: Aslak Hellesøy (aslak_hellesoy)
Date: 2006-11-26 19:40

Message:
Reorganising things is the kind of thing that is hard to submit a patch for. It's just a bunch of svn mv (plus a little rake hacking). Let's discuss the proposed layout here. This is my initial suggestion (everything is under trunk)

Rakefile # Delegates to sub Rakefiles - for running *all* specs
rspec/init.rb # The core - requires the three subprojects, each of which have their own lib and spec dir
rspec/expectations
rspec/context_runner
rspec/mocks
jruby/
RSpec.tmbundle/
rspec_on_rails/
rspec_on_rails_demo/ # Could pull in rspec_on_rails via svn:external
selenium/
watir/

This organisation would allow Rails projects to install RSpec as 2 Rails plugins: rspec and rspec_on_rails

WDYT?

----------------------------------------------------------------------

Comment By: Pat Maddox (pergesu)
Date: 2006-11-26 19:18

Message:
"And, of course, bugs and RFEs are most welcome. Feel free
to contribute patches as well."

That's what I meant by bang out bugs and RFEs :)  I'll go
through the list and write patches, as well as come up with
whatever other patches I need as I write my Rails app.  Just
kinda tough with the current structure...any timeline on
when things will be cleaner?

----------------------------------------------------------------------

Comment By: David Chelimsky (dchelimsky)
Date: 2006-11-26 19:13

Message:
Absolutely! We've been wanting to restructure things and this is one of the issues under discussion. We'll address this soon. When we're ready to, there will be an email to the list in advance so that those who do prefer to work from source won't be all screwed up by it.

And, of course, bugs and RFEs are most welcome. Feel free to contribute patches as well.

Cheers,
David

----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=3152&aid=6898&group_id=797


More information about the rspec-devel mailing list