Fixing gem grouping and simplecov version #34
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* The latest simplecov is broken, and causes an error on irb exit * Using fuubar in the development group causes a warning on irb start
christiannelson
added a commit
that referenced
this pull request
Mar 5, 2014
Fixing gem grouping and simplecov version.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This fixes two warnings/errors:
The latest simplecov is not working properly (see simplecov-ruby/simplecov#281), and it calls
exitwithin aKernel.at_exit, which causes irb to explode on exit.With fuubar in the development group, this warning is logged on irb start, because fuubar requires rspec:
irb: warn: can't alias context from irb_context.On a related note, should more of the gems in the :development/:test combined group be moved to only test? For example, I see jasminerice routes in
rake routes