Skip to content
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

--rspec option not respected on gem creation #277

Open
dgmora opened this issue Oct 22, 2015 · 3 comments
Open

--rspec option not respected on gem creation #277

dgmora opened this issue Oct 22, 2015 · 3 comments
Labels

Comments

@dgmora
Copy link

dgmora commented Oct 22, 2015

With the following options (in 2.0.1) :

jeweler --rspec --shoulda  --user-name dgmora --user-email david@somewhere.com --github-username dgmora --git-remote heythere --create-repo --yard heythere

rspec folder is not created, TestUnit is used instead:

create  .gitignore
create  Rakefile
create  Gemfile
create  LICENSE.txt
create  README.rdoc
create  .document
create  lib
create  lib/heythere.rb
create  test
create  test/helper.rb
create  test/test_heythere.rb

If I swap --rspec and --shoulda options, the rspec folder is generated as expected.

@flajann2
Copy link
Collaborator

Is this still the case? If so I will fix it shortly.

@dgmora
Copy link
Author

dgmora commented May 18, 2016

yes, it is. I am not sure though, that those flags where expected to be used together (or what should it produce). I try that because sometimes with Rails I used RSpec + Shoulda together

@technicalpickles
Copy link
Owner

Jeweler's use of shoulda predates when it could be used with RSped as matchers. I'm not kept up with shoulda to know if it is even usable by itself without RSpec. If it can't then it'd make sense to remove/deprecate the option.

@flajann2 flajann2 added the bug label Oct 22, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants