thoughtbot--shoulda-matchers/Gemfile.lock

GEM
  remote: https://rubygems.org/
  specs:
    appraisal (2.1.0)
      bundler
      rake
      thor (>= 0.14.0)
    byebug (9.0.6)
    coderay (1.1.1)
    diff-lcs (1.2.5)
    fssm (0.2.10)
    method_source (0.8.2)
    multi_json (1.12.1)
    pry (0.10.4)
      coderay (~> 1.1.0)
      method_source (~> 0.8.1)
      slop (~> 3.4)
    pry-byebug (3.4.2)
      byebug (~> 9.0)
      pry (~> 0.10)
    pygments.rb (1.1.1)
      multi_json (>= 1.0.0)
    rake (10.5.0)
    redcarpet (3.4.0)
    rspec (3.5.0)
      rspec-core (~> 3.5.0)
      rspec-expectations (~> 3.5.0)
      rspec-mocks (~> 3.5.0)
    rspec-core (3.5.4)
      rspec-support (~> 3.5.0)
    rspec-expectations (3.5.0)
      diff-lcs (>= 1.2.0, < 2.0)
      rspec-support (~> 3.5.0)
    rspec-mocks (3.5.0)
      diff-lcs (>= 1.2.0, < 2.0)
      rspec-support (~> 3.5.0)
    rspec-support (3.5.0)
    slop (3.6.0)
    thor (0.19.4)
    yard (0.9.6)
    zeus (0.15.14)
      method_source (>= 0.6.7)

PLATFORMS
  ruby

DEPENDENCIES
  appraisal (~> 2.0)
  bundler (~> 1.1)
  fssm
  pry
  pry-byebug
  pygments.rb
  rake (>= 10.5.0, < 11)
  redcarpet
  rspec (~> 3.2)
  yard
  zeus

BUNDLED WITH
   1.14.6
Unignore Gemfile.lock, per Appraisal instructions. 2012-04-10 00:08:10 -04:00			`GEM`
Rename failure_message and negative_failure_message * fixes #108 : RSpec 2.10 compatibility * remove unnecessary attr_readr 2013-01-08 12:29:01 -05:00			`remote: https://rubygems.org/`
Unignore Gemfile.lock, per Appraisal instructions. 2012-04-10 00:08:10 -04:00			`specs:`
Bump Appraisal to 2.1.0 Why: * At some point a while back, Appraisal introduced a bug fix that made it possible to run `rspec` through `appraisal` and pass the `-e` option to target certain tests. This makes life much easier. * It's been a while since we've upgraded Appraisal anyway. 2015-09-25 18:15:01 -04:00			`appraisal (2.1.0)`
Unignore Gemfile.lock, per Appraisal instructions. 2012-04-10 00:08:10 -04:00			`bundler`
			`rake`
Use the new appraisal executable in 1.0.0.beta1 2014-01-20 13:39:18 -05:00			`thor (>= 0.14.0)`
Mass-update all dev dependencies 2017-01-09 11:55:12 -05:00			`byebug (9.0.6)`
			`coderay (1.1.1)`
Changed copyright at bottom of README also 2014-01-21 23:22:31 -05:00			`diff-lcs (1.2.5)`
Manually autogenerate docs Why: * The guard-yard gem doesn't seem to work so well anymore. In fact, the problem is with `yard server` -- it doesn't seem to use our custom template files. To satisfy the above: * Instead of using Guard and guard-yard, use the fssm gem to manually watch various files. * Instead of using `yard server`, run `yard doc`, which does honor our custom template files. * You can run `rake autogenerate_docs` to make this happen; update the README accordingly. [ci skip] 2015-09-23 15:44:42 -04:00			`fssm (0.2.10)`
Add pry as development dependency 2014-02-09 07:22:25 -05:00			`method_source (0.8.2)`
Mass-update all dev dependencies 2017-01-09 11:55:12 -05:00			`multi_json (1.12.1)`
Update zeus & pry so that we can use Zeus again 2017-07-24 21:54:43 -04:00			`pry (0.10.4)`
			`coderay (~> 1.1.0)`
			`method_source (~> 0.8.1)`
			`slop (~> 3.4)`
Mass-update all dev dependencies 2017-01-09 11:55:12 -05:00			`pry-byebug (3.4.2)`
			`byebug (~> 9.0)`
Use pry-byebug instead of pry-nav 2015-04-02 11:42:53 -04:00			`pry (~> 0.10)`
Mass-update all dev dependencies 2017-01-09 11:55:12 -05:00			`pygments.rb (1.1.1)`
			`multi_json (>= 1.0.0)`
Upgrade Rake This is necessary in order to use Zeus, since Rake is loaded before Bundler (and so if the version of Rake installed locally and the version in the Gemfile differ then Bundler will complain). 2016-01-25 00:08:55 -05:00			`rake (10.5.0)`
Mass-update all dev dependencies 2017-01-09 11:55:12 -05:00			`redcarpet (3.4.0)`
			`rspec (3.5.0)`
			`rspec-core (~> 3.5.0)`
			`rspec-expectations (~> 3.5.0)`
			`rspec-mocks (~> 3.5.0)`
			`rspec-core (3.5.4)`
			`rspec-support (~> 3.5.0)`
			`rspec-expectations (3.5.0)`
Using RSpec 3 for development. 2014-06-17 00:54:02 -04:00			`diff-lcs (>= 1.2.0, < 2.0)`
Mass-update all dev dependencies 2017-01-09 11:55:12 -05:00			`rspec-support (~> 3.5.0)`
			`rspec-mocks (3.5.0)`
Upgrade rspec 2015-10-08 01:26:48 -04:00			`diff-lcs (>= 1.2.0, < 2.0)`
Mass-update all dev dependencies 2017-01-09 11:55:12 -05:00			`rspec-support (~> 3.5.0)`
			`rspec-support (3.5.0)`
Update zeus & pry so that we can use Zeus again 2017-07-24 21:54:43 -04:00			`slop (3.6.0)`
Mass-update all dev dependencies 2017-01-09 11:55:12 -05:00			`thor (0.19.4)`
			`yard (0.9.6)`
Update zeus & pry so that we can use Zeus again 2017-07-24 21:54:43 -04:00			`zeus (0.15.14)`
Speed up running unit tests with Zeus This is an effort to vastly decrease the time it takes to run a single unit test file and therefore increase productivity and happiness for people working on this project. If you want to run a unit test file, now you can use `zeus rspec` instead of `rspec` -- assuming you run `zeus start` first -- and it will run a LOT faster. Because test files tend to have long file paths, you can even use a shorter version of those paths. So instead of saying: zeus rspec spec/unit/shoulda/matchers/active_record/validate_uniqueness_of_matcher_spec.rb you can say: zeus rspec active_record/validate_uniqueness_of_matcher_spec.rb 2015-11-29 20:57:45 -05:00			`method_source (>= 0.6.7)`
Unignore Gemfile.lock, per Appraisal instructions. 2012-04-10 00:08:10 -04:00
			`PLATFORMS`
			`ruby`

			`DEPENDENCIES`
Bump Appraisal to 2.1.0 Why: * At some point a while back, Appraisal introduced a bug fix that made it possible to run `rspec` through `appraisal` and pass the `-e` option to target certain tests. This makes life much easier. * It's been a while since we've upgraded Appraisal anyway. 2015-09-25 18:15:01 -04:00			`appraisal (~> 2.0)`
Whoops, don't use Bundler 1.0 2012-09-21 15:19:41 -04:00			`bundler (~> 1.1)`
Manually autogenerate docs Why: * The guard-yard gem doesn't seem to work so well anymore. In fact, the problem is with `yard server` -- it doesn't seem to use our custom template files. To satisfy the above: * Instead of using Guard and guard-yard, use the fssm gem to manually watch various files. * Instead of using `yard server`, run `yard doc`, which does honor our custom template files. * You can run `rake autogenerate_docs` to make this happen; update the README accordingly. [ci skip] 2015-09-23 15:44:42 -04:00			`fssm`
Update zeus & pry so that we can use Zeus again 2017-07-24 21:54:43 -04:00			`pry`
Use pry-byebug instead of pry-nav 2015-04-02 11:42:53 -04:00			`pry-byebug`
Generate docs using YARD 2014-06-20 00:44:06 -04:00			`pygments.rb`
Upgrade Rake This is necessary in order to use Zeus, since Rake is loaded before Bundler (and so if the version of Rake installed locally and the version in the Gemfile differ then Bundler will complain). 2016-01-25 00:08:55 -05:00			`rake (>= 10.5.0, < 11)`
Generate docs using YARD 2014-06-20 00:44:06 -04:00			`redcarpet`
Upgrade rspec 2015-10-08 01:26:48 -04:00			`rspec (~> 3.2)`
Generate docs using YARD 2014-06-20 00:44:06 -04:00			`yard`
Speed up running unit tests with Zeus This is an effort to vastly decrease the time it takes to run a single unit test file and therefore increase productivity and happiness for people working on this project. If you want to run a unit test file, now you can use `zeus rspec` instead of `rspec` -- assuming you run `zeus start` first -- and it will run a LOT faster. Because test files tend to have long file paths, you can even use a shorter version of those paths. So instead of saying: zeus rspec spec/unit/shoulda/matchers/active_record/validate_uniqueness_of_matcher_spec.rb you can say: zeus rspec active_record/validate_uniqueness_of_matcher_spec.rb 2015-11-29 20:57:45 -05:00			`zeus`
Upgrade RSpec to v3.4 v3.3 introduced a new feature: the ability to re-run failed specs. v3.4 contains some other nifty features, such as code highlighting and compound failure messages. 2015-12-23 01:46:29 -05:00
			`BUNDLED WITH`
Update zeus & pry so that we can use Zeus again 2017-07-24 21:54:43 -04:00			`1.14.6`