Skip to content
This repository

Jan 29, 2013

  1. Matt Jankowski

    Bump rails gem versions to latest for Appraisal

    authored January 29, 2013

Jan 07, 2013

  1. Matt Jankowski

    Allow Rails 3.1 to select the 'turn' gem it wants to use

    Rails 3.1.x has code which checks which version of ruby is being run,
    and based on the result, selects a version of turn.
    
    For 1.9.3+, it selects "~> 0.8.3"; for everything else, it selects "0.8.2".
    
    If we remove turn from the Appraisals, but have travis install both versions
    that rails might potentially need, the in-generated-app Gemfile building should
    work correctly.
    authored January 07, 2013
  2. Matt Jankowski

    Newer versions of activerecord-jdbcsqlite3-adapter work without a spe…

    …cially named db driver in database.yml
    authored January 07, 2013
  3. Matt Jankowski

    Allow each Appraisal version gemfile to resolve the exact gem version…

    …s needed
    authored January 07, 2013

Jan 04, 2013

  1. Matt Jankowski

    Update rails gem versions in Appraisals to use latest stable releases…

    …: 3.2.10, 3.1.9, 3.0.18
    authored January 04, 2013
  2. Matt Jankowski

    Be more specific about which gems are required for which rails versio…

    …ns via Appraisals
    authored January 04, 2013

Dec 13, 2012

  1. Matt Jankowski

    jruby needs a separate sqlite3 adapter

    authored December 13, 2012
  2. Matt Jankowski

    Bump the rails 3.2.8 appraisal to 3.2.9

    authored December 13, 2012
  3. Matt Jankowski

    Use minitest-rails only when we actually want to test it.

    Some features test the factory_girl_rails integration with minitest-rails.
    
    Other features just test normal integration with rails generators.
    
    When minitest-rails is *always* in our gemfiles, minitest's generator
    gets run during the features which generate new rails apps.
    
    Because minitest doesnt support namespaced models, this fails.  But, also,
    we don't actually want to run minitest during anything other than the specific
    areas where we are testing that integration.
    
    Thus, we need the gem present on the system, but not in the gemfiles during
    any times other than when it's pulled in specifically by those features.
    authored December 13, 2012
Something went wrong with that request. Please try again.