guard-rspec 2.5.2 → 2.5.3

checksums.yaml

@@ -1,15 +1,7 @@
 ---
-!binary "U0hBMQ==":
-  metadata.gz: !binary |-
-    ODNjNWI3NmZjZjM2MjkzNThmNmZmMWM2M2U4NjcwOTcxMDdiY2M3Ng==
-  data.tar.gz: !binary |-
-    ZjczOTFlZmU1NTEwYTYxMWM2NWU4Yjg1NDZmMmEyMjM1MmEwYmI3NA==
-!binary "U0hBNTEy":
-  metadata.gz: !binary |-
-    NTMxNzhmZDQyYmU4NGQ0ZTQ5Y2I0NThjYWU3MGYwYWEwOGUxNDg3ZTVjNmZj
-    YWJhOTkxZDAwZWY0NWFhOGFjY2E0YjY2ODczYjQxYmNjNjE1NTg3YjEyMTcw
-    MDU5ZWRlODhiOTg2NDIyYjk3OTk0NDdmYzdmM2I0NmZmOTgwYTA=
-  data.tar.gz: !binary |-
-    NjgwNzJjYzBhNzBkY2UzOTUxZDZmYzM2YWE2YzQ0ZDFkMjQ2NTY4YWUwNmMy
-    OWQ1MmNlYjM1OGQxZThjNGQ0OTJmNGVhY2ExYjM4ZmFlNWY2YjA0YjczZTUy
-    YmQ0YWIxNjNjNGRlY2RlYWRjOGM5ZmZmMWZlNDQyOWExN2NlYTc=
+SHA1:
+  metadata.gz: 6cb8628e7c26ce4ae2f79eaad2450439a2f3b699
+  data.tar.gz: 489f1c1af197a01ba1db0dba936b93046fb0e2e5
+SHA512:
+  metadata.gz: f169bcda81fcfbd228cfda8c28b3001d82754e65aa703f7941f06e4e6597e4de67cc8b40214781e80171dff930ccfee96334479434d6a35bcd54796f3d51809e
+  data.tar.gz: 4c7cc24c868566a1dbf2a637f5c831f5cb5b86dd3f0c4b1c3689b98390551d5976848e0ce109b7031a7712d7b02945ac5b01b2268d32a86b5d5f9c690298a972

data/README.md

@@ -7,7 +7,7 @@ RSpec guard allows to automatically & intelligently launch specs when files are
 
 ## Install
 
-Please be sure to have [Guard](https://github.com/guard/guard) installed before continue.
+Please be sure to have [Guard](https://github.com/guard/guard) installed before continuing.
 
 Install the gem:
 
@@ -31,11 +31,11 @@ $ guard init rspec
 
 ## Usage
 
-Please read [Guard usage doc](https://github.com/guard/guard#readme)
+Please read [Guard usage doc](https://github.com/guard/guard#readme).
 
 ## Guardfile
 
-RSpec guard can be really adapted to all kind of projects.
+RSpec guard can be adapted to all kinds of projects.
 
 ### Standard RubyGem project
 
@@ -81,14 +81,14 @@ guard 'rspec', :spec_paths => ["spec", "vendor/engines/reset/spec"] do
   # ...
 end
 ```
-If you have only one path to look, you can configure `:spec_paths` option with a string:
+If you have only one path to look in, you can configure the `:spec_paths` option with a string:
 
 ``` ruby
 guard 'rspec', :spec_paths => "test" do
   # ...
 end
 ```
-If you want to set an environment variable, you can configure `:env` option with a hash:
+If you want to set an environment variable, you can configure the `:env` option with a hash:
 
 ``` ruby
 guard 'rspec', :env => {'RAILS_ENV' => 'guard'} do
@@ -114,7 +114,7 @@ guard 'rspec', :parallel => true, :parallel_cli => '-n 2' do
 end
 ```
 
-Former `:color`, `:drb`, `:fail_fast` and `:formatter` options are deprecated and have no effect anymore.
+Former `:color`, `:drb`, `:fail_fast` and `:formatter` options are deprecated and no longer have effect.
 
 ### List of available options:
 
@@ -144,7 +144,7 @@ You can also use a custom binstubs directory using `:binstubs => 'some-dir'`.
 
 When you specify `--drb` within `:cli`, guard-rspec will circumvent the `rspec` command line tool by
 directly communicating with the RSpec DRb server.  This avoids the extra overhead incurred by your
-shell, bundler and loading RSpec's environment just to send a DRb message.  It shaves off a
+shell, bundler and loading RSpec's environment just to send a DRb message. It shaves off a
 second or two before the specs start to run; they should run almost immediately.
 
 ## Notification
@@ -157,7 +157,7 @@ The best solution is still to update RSpec to the latest version!
 
 ## Formatters
 
-The `:formatter` option has been removed since CLI arguments can be passed through the `:cli` option. If you want to use the former Instafail formatter, you need to use [rspec-instafail](http://rubygems.org/gems/rspec-instafail) gem instead:
+The `:formatter` option has been removed since CLI arguments can be passed through the `:cli` option. If you want to use the former Instafail formatter, you need to use the [rspec-instafail](http://rubygems.org/gems/rspec-instafail) gem instead:
 
 ``` ruby
 # in your Gemfile
@@ -173,12 +173,12 @@ Default formatter is the `progress` formatter (same as RSpec default).
 
 ## Running a subset of all specs
 
-The `:all_on_start` and `:all_after_pass` options cause all specs located in the `spec` directory to be run.  If there
+The `:all_on_start` and `:all_after_pass` options cause all specs located in the `spec` directory to be run. If there
 are some specs you want to skip, you can tag them with RSpec metadata (such as `:slow => true`)
 and skip them with the cli `--tag` option (i.e. `--tag ~slow`).
 
 You can also use option :spec_paths to override paths used when running all specs.
-You can use this feature to create multiple groups of guarded specs with distinct paths, and execute each in own process:
+You can use this feature to create multiple groups of guarded specs with distinct paths, and execute each in its own process:
 
 ``` ruby
 # in your Guardfile

data/lib/guard/rspec/runner.rb

@@ -167,7 +167,7 @@ module Guard
         # Make sure we have a listener running
         unless @drb_listener_running
           begin
-            DRb.start_service("druby://localhost:0")
+            DRb.start_service("druby://127.0.0.1:0")
           rescue SocketError, Errno::EADDRNOTAVAIL
             DRb.start_service("druby://:0")
           end

data/lib/guard/rspec/version.rb

@@ -1,5 +1,5 @@
 module Guard
   module RSpecVersion
-    VERSION = "2.5.2"
+    VERSION = "2.5.3"
   end
 end

metadata

@@ -1,27 +1,27 @@
 --- !ruby/object:Gem::Specification
 name: guard-rspec
 version: !ruby/object:Gem::Version
-  version: 2.5.2
+  version: 2.5.3
 platform: ruby
 authors:
 - Thibaud Guillaume-Gentil
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2013-04-02 00:00:00.000000000 Z
+date: 2013-04-12 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: guard
   requirement: !ruby/object:Gem::Requirement
     requirements:
-    - - ! '>='
+    - - '>='
       - !ruby/object:Gem::Version
         version: '1.1'
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
-    - - ! '>='
+    - - '>='
       - !ruby/object:Gem::Version
         version: '1.1'
 - !ruby/object:Gem::Dependency
@@ -76,12 +76,12 @@ require_paths:
 - lib
 required_ruby_version: !ruby/object:Gem::Requirement
   requirements:
-  - - ! '>='
+  - - '>='
     - !ruby/object:Gem::Version
       version: '0'
 required_rubygems_version: !ruby/object:Gem::Requirement
   requirements:
-  - - ! '>='
+  - - '>='
     - !ruby/object:Gem::Version
       version: 1.3.6
 requirements: []