delta/bundler.git, branch seg-error-report-command

[ErrorReport] Print the command that was run

2015-05-02T18:56:17+00:00

Merge pull request #3608 from bundler/seg-stubs-for

2015-05-02T03:07:46+00:00

[RubyGemsIntegration] Use .stubs_for when available

[RubyGemsIntegration] Use .stubs_for when available

2015-05-01T00:43:29+00:00

Merge pull request #3584 from hiukkanen/lint-fix

2015-04-30T07:43:28+00:00

Use include expectation instead of unneeded regular expression

Move RubyGems 2.4.7 compatibility into 2.1+

2015-04-30T07:36:18+00:00

Merge pull request #3606 from tenderlove/spec_search

2015-04-30T07:18:58+00:00

loop through the spec list to find gems with a certain name

Merge pull request #3603 from amatsuda/bundle_gem_hyphenated_gem_name_starting_with_an_existing_const

2015-04-30T07:10:15+00:00

Bundler >= 1.9.0 fails to create gem plugins

Merge pull request #3602 from pducks32/fix-ignore-messages

2015-04-30T04:10:56+00:00

Fix ignore messages

Merge pull request #3580 from bundler/seg-stubs

2015-04-30T04:10:29+00:00

Use specification stubs with RubyGems 2.1+ when constructing the local i...

A gem extending an existing const should be creatable

2015-04-30T03:13:28+00:00

Since 17a4fc47bfad02de553e5a53b00ad38b4c905e18, any gem name starting with an
existing const name has been regarded as "Invalid gem name" by `bundle gem` command.
However, "gem-foo" or "rails-bar" should be totally valid and rather preferable
naming for plugins for RubyGems/Rails.

This commit changes the rule to raise error only when the new gem name fully
matches an existing const name.