torquebox-sidekiq-service 0.1.1 → 0.1.2

data/VERSION

@@ -1 +1 @@
-0.1.1
+0.1.2

data/lib/torquebox-sidekiq-service.rb

@@ -1,10 +1,11 @@
 # This is needed to make Sidekiq think it's working in a server capacity.
 module Sidekiq
-  class CLI
-  end
+  class Shutdown < RuntimeError; end
+
+  class CLI; end
 end
 
 # Sidekiq requires its processor to be available if configuring server middleware.
 require 'sidekiq/processor'
 
-require 'torque_box/sidekiq_service'
+require 'torque_box/sidekiq_service'

data/torquebox-sidekiq-service.gemspec

@@ -5,11 +5,11 @@
 
 Gem::Specification.new do |s|
   s.name = "torquebox-sidekiq-service"
-  s.version = "0.1.1"
+  s.version = "0.1.2"
 
   s.required_rubygems_version = Gem::Requirement.new(">= 0") if s.respond_to? :required_rubygems_version=
   s.authors = ["Kevin Menard"]
-  s.date = "2013-03-29"
+  s.date = "2013-04-30"
   s.description = "    The TorqueBox Sidekiq service replaces the traditional Sidekiq CLI client for starting a Sidekiq processor.  This\n    allows TorqueBox features only available in-container to be usable by all your Sidekiq workers.  It has the added\n    benefit of reducing memory overhead by running in a single JVM and allows for better optimization through JIT and\n    better debugging & profiling through TorqueBox's runtime inspection facilities.\n"
   s.email = "nirvdrum@gmail.com"
   s.extra_rdoc_files = [
@@ -47,12 +47,14 @@ Gem::Specification.new do |s|
       s.add_development_dependency(%q<jeweler>, [">= 0"])
       s.add_development_dependency(%q<jeweler>, [">= 0"])
       s.add_development_dependency(%q<jeweler>, [">= 0"])
+      s.add_development_dependency(%q<jeweler>, [">= 0"])
     else
       s.add_dependency(%q<torquebox-sidekiq-service>, [">= 0"])
       s.add_dependency(%q<sidekiq>, [">= 0"])
       s.add_dependency(%q<jeweler>, [">= 0"])
       s.add_dependency(%q<jeweler>, [">= 0"])
       s.add_dependency(%q<jeweler>, [">= 0"])
+      s.add_dependency(%q<jeweler>, [">= 0"])
     end
   else
     s.add_dependency(%q<torquebox-sidekiq-service>, [">= 0"])
@@ -60,6 +62,7 @@ Gem::Specification.new do |s|
     s.add_dependency(%q<jeweler>, [">= 0"])
     s.add_dependency(%q<jeweler>, [">= 0"])
     s.add_dependency(%q<jeweler>, [">= 0"])
+    s.add_dependency(%q<jeweler>, [">= 0"])
   end
 end
 

metadata

@@ -1,15 +1,15 @@
 --- !ruby/object:Gem::Specification
 name: torquebox-sidekiq-service
 version: !ruby/object:Gem::Version
+  version: 0.1.2
   prerelease:
-  version: 0.1.1
 platform: ruby
 authors:
 - Kevin Menard
 autorequire:
 bindir: bin
 cert_chain: []
-date: 2013-03-29 00:00:00.000000000 Z
+date: 2013-04-30 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: torquebox-sidekiq-service
@@ -101,6 +101,24 @@ dependencies:
     none: false
   prerelease: false
   type: :development
+- !ruby/object:Gem::Dependency
+  name: jeweler
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: !binary |-
+          MA==
+    none: false
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: !binary |-
+          MA==
+    none: false
+  prerelease: false
+  type: :development
 description: |2
       The TorqueBox Sidekiq service replaces the traditional Sidekiq CLI client for starting a Sidekiq processor.  This
       allows TorqueBox features only available in-container to be usable by all your Sidekiq workers.  It has the added
@@ -138,10 +156,10 @@ required_ruby_version: !ruby/object:Gem::Requirement
   requirements:
   - - ">="
     - !ruby/object:Gem::Version
-      version: !binary |-
-        MA==
       segments:
       - 0
+      version: !binary |-
+        MA==
       hash: 2
   none: false
 required_rubygems_version: !ruby/object:Gem::Requirement