Update to recent bundler #107
Open
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
…e for the complete project and the specific ocra executable. You can now refer to a gemfile that is structured with groups and only include the gems that are relevant (in the below case ‘tiny_tds’) source 'https://rubygems.org' group :development do gem 'pry' gem ‘ocra’ end gem 'tiny_tds'
|
Thanks for the submission, but I have tried with Bundler 1.10.6 and Ruby 2.2.3p173 and can't reproduce any issue. Can you provide more details and a test-case or example that doesn't work? |
larsch
force-pushed
the
master
branch
2 times, most recently
from
b897a6e
to
2e7c88f
Compare
|
I'm using bundler 1.11.2, but ruby 2.1.7. I'll try to make a test project to show the behaviour. Do you think the "groups" are a good idea? (group :development do) |
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.
The latest bundler doesn't reload the environment when load.specs is called (it's memoized), so the gemfile option is not respected.
Update to recent bundler, and make it possible to use the same gemfile for the complete project and the specific ocra executable.
You can now refer to a gemfile that is structured with groups and only include the gems that are relevant (in the below case ‘tiny_tds’)
source 'https://rubygems.org'
group :development do
gem 'pry'
gem ‘ocra’
end
gem 'tiny_tds'
I also changed that including the gemfile would not check the loaded gems, as in my usecase this would include additional gems I don't use in the executable (for example ocra itself).