-
Notifications
You must be signed in to change notification settings - Fork 21.9k
Description
Bundler 1.12 seems to refuse to do any bundle operations if the Gemfile is considered 'invalid' becuase it has TODO
in the summary/author/etc, which is how default gemfiles are generated.
This means the final bundle install
of the generator script does not work, so you don't actually have a bundled app. I don't think the plugin script contains any post_bundle
hooks, so it's not as bad as it could be -- any post_bundle
hooks probably won't run at all, or won't work properly. (Third party software providing generators building on plugin new could provide such post_bundle hooks, and be broken worse).
With Bundler 1.13 there's a different(?) worse problem, but I assume if that problem were resolved this one would still be waiting.
$ ruby -v
ruby 2.3.1p112 (2016-04-26 revision 54768) [x86_64-darwin15]
$ rails -v
Rails 5.0.0.1
$ bundle -v
Bundler version 1.12.5
$rails plugin new testplugin
create
create README.md
create Rakefile
create testplugin.gemspec
create MIT-LICENSE
create .gitignore
create Gemfile
create lib/testplugin.rb
create lib/tasks/testplugin_tasks.rake
create lib/testplugin/version.rb
create bin/test
create test/test_helper.rb
create test/testplugin_test.rb
append Rakefile
vendor_app test/dummy
run bundle install
You have one or more invalid gemspecs that need to be fixed.
The gemspec at /Users/jrochkind/code/testplugin/testplugin.gemspec is not valid. Please fix this gemspec.
The validation error was '"FIXME" or "TODO" is not a description'
With bundler 1.11.2, this does not reproduce, the rails plugin new
completes without errors, and the bundle install
happens.