Permalink
Switch branches/tags
Commits on May 27, 2012
  1. Version 1.1.4 with changelog

    indirect committed May 27, 2012
  2. grammar fix for spec name

    indirect committed May 27, 2012
  3. add vendored_persistent

    This clears up fetcher.rb's implicit dependency on being loaded after vendored_thor (which added lib/vendor/ to the load path).
    indirect committed May 27, 2012
  4. revamp ISSUES

     - remove frequent issues that aren't so frequent anymore
     - move Heroku instructions first, rewrite for clarity
     - link directly to the new ticket page
    indirect committed May 27, 2012
  5. fixes for capistrano integration

    switch the bundler hook to before "deploy:finalize_update", so that finalize_update will not run if `bundle install` fails. (thanks @leehambley)
    
    change from `current_release` to `latest_release`, because both cap and vlad provide more robust directory-finding code behind `latest_release`. (thanks @dontangg)
    
    closes #1264
    indirect committed May 23, 2012
Commits on May 24, 2012
  1. Fixing "bundle clean --force" banner.

    The --force option was incorrectly stating that it forces a clean if --path IS set. It actually forces a clean if --path is NOT set.
    dougbarth committed with hone May 10, 2012
Commits on Mar 24, 2012
  1. Bundler 1.1.3

    hone committed Mar 24, 2012
  2. update changelog for 1.1.3

    hone committed Mar 24, 2012
Commits on Mar 23, 2012
Commits on Mar 21, 2012
  1. Bundler 1.1.2

    hone committed Mar 21, 2012
  2. update changelog for 1.1.2

    hone committed Mar 21, 2012
  3. Fixes #1782. Don't remove duplicate PATH sources

    When using specifying version number, you can have multiple PATH
    sections for the same source.
    
    We were over eager in
    e31a1c7#L1R51.
    We should only remove the duplicate GIT sources, so let's explicitly
    check for that.
    hone committed Mar 21, 2012
  4. Test case for bundle install not checking out git

    During the 1.1 pre/RC releases, there were duplicate GIT source sections
    generated in the `Gemfile.lock`. These would confuse bundler and the
    wrong source would get attached to the spec. This test case breaks if we
    don't fix this here:
    e31a1c7#L1R51
    hone committed Mar 21, 2012
Commits on Mar 14, 2012
  1. Bundler 1.1.1

    hone committed Mar 14, 2012
  2. update changelog for 1.1.1

    hone committed Mar 14, 2012
  3. fix bundle cache edge case for #1202

    hone committed Mar 14, 2012
Commits on Mar 13, 2012
  1. Changelog for 1.1.1

    indirect committed Mar 13, 2012
Commits on Mar 11, 2012
  1. fix void use of == warning

    indirect committed Mar 11, 2012
  2. fix shadowed variable warning

    indirect committed Mar 11, 2012
  3. raising Gem::InstallError is the worst possible thing

    This code meant that _any_ gem install failure resulted in a message requesting the user to report this "bug" to the Bundler issue tracker. That is very, very not cool, and I had already fixed this issue once before the hook pull request regressed it. :(
    indirect committed Mar 11, 2012