resque-workers-lock 1.7 → 1.8

data/README.md

@@ -5,6 +5,8 @@ This is a [resque](https://github.com/defunkt/resque) plugin inspired by [resque
 gem 'resque-workers-lock'
 ```
 
+**Important notice** - As of version 1.7, Resque Workers Lock no longer includes a enqueue lock but focusses solely on a workers lock. If you're also looking for enqueue lock functionality, just add [resque-lock](https://github.com/defunkt/resque-lock) or another plugin in the mix.
+
 ## What does it do?
 If resque jobs have the same lock applied this means that those jobs cannot be processed simultaneously by two or more workers. When this situation occurs the second job gets pushed back to the queue.
 
@@ -61,25 +63,6 @@ Please note that setting this value to 5 seconds will keep the worker idle for 5
 ## Possibilities to prevent the loop
 Do a delayed resque (re)queue. However, this will have approximately the same results and will require a large extra chunk of code and rake configurations.
 
-## Run workers for the test
-To run the tests using `rake test` properly, make sure there are a few workers running:
-```
-$ redis-server
-$ VVERBOSE=1 COUNT=4 QUEUE=* rake resque:work
-```
-
-```
-➜  resque-workers-lock git:(master) ✗ rake test
-Run options: 
-
-# Running tests:
-
-...
-
-Finished tests in 10.426519s, 0.2877 tests/s, 0.3836 assertions/s.
-
-3 tests, 4 assertions, 0 failures, 0 errors, 0 skips
-```
-
 ## Authors/Contributors
 [nicholaides](https://github.com/nicholaides)
+[jgarber](https://github.com/jgarber)

metadata

@@ -1,16 +1,17 @@
 --- !ruby/object:Gem::Specification
 name: resque-workers-lock
 version: !ruby/object:Gem::Version
-  version: '1.7'
+  version: '1.8'
   prerelease: 
 platform: ruby
 authors:
 - Bart Olsthoorn
 - Mike Nicholaides
+- Jason Garber
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2012-12-19 00:00:00.000000000 Z
+date: 2013-02-04 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: resque