Then I can't explain it. I've seen that problem before where the
project is under svn but vendor/plugins doesn't exist until you try to
install a plugin, and then you have explicitly add vendor/plugins to
svn. But if your vendor/plugins is definitely under version control
(i.e. svn info vendor/plugins gives you the right information) then I
have no idea what would be causing it. Sorry.
I see you’re running Windows. If you’re using the svn ASP.NET hack such that your svn admin dirs are _svn instead of .svn, then script/plugin install -x doesn’t work. I submitted a patch to Rails not that long ago: http://dev.rubyonrails.org/ticket/9007. If you are indeed using the svn ASP.NET hack, please write to the Rails core mailing list [
http://groups.google.com/group/rubyonrails-core ] and ask for the patch to be reviewed. I asked when I submitted the patch, but nobody has commented on it yet.
Of course, you could just set svn:externals on vendor/plugins to reference the rspec and rspec_on_rails plugins. Some people don’t like to do that, though, because it makes them dependent on external svn servers being up, among other reasons.
Very true, but it was so painfully slow for me when I last tried it
that I abandoned it for that little project. Perhaps your project
will fare better.