-
-
Notifications
You must be signed in to change notification settings - Fork 1k
gemspec removed from git #3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
gem "rspec-rails", :version => ">= 2.0.0.beta.1" Works just fine. |
I'd prefer people use the published gems. If you use github as a source there's no guarantee you'll ever get anything that works. |
Ack, thanks for the no confirm delete github, I did not mean to click that. |
Did you delete your comment? |
I did not mean to delete the one between your two above there, yes. |
I think most of us know that when we use the edge version of a repository we have some chances to break everything. But the opposite also works. You've committed 572a81108a, which should allow us to test the controllers. Without that commit, we can't launch our controller specs without having the error I think you should let people decide whether they want to use the committed version or a repository commit. |
I restored the gemspec - we'll see how it goes. |
Thank you. |
"You passed :version as an option for gem 'rspec-rails', but it is invalid." Should be: |
@levifig - this issue is already closed. Please report any new issues in a separate github issue. When you do, please tell me what command you are running to get this feedback. Thanks. |
Why was this removed from git? You can no longer use bundle install in Rails 3 to grab the latest version of rspec-rails.
The text was updated successfully, but these errors were encountered: