rakegrowl 0.3.0 → 0.3.1

data/README.md

@@ -1,4 +1,4 @@
-# rakegrowl
+# Rakegrowl [![Build Status](https://secure.travis-ci.org/porras/rakegrowl.png)](http://travis-ci.org/porras/rakegrowl)
 
 Do you recognize this situation? You run a `rake` task (for example, `rake spec`), which you know it's going to take some time (e.g. 3 or 4 minutes). You say _"Great moment to check what's going on on Twitter"_. 10 minutes and 3 tabs with blog posts later, you realize you were actually waiting for a task to finish, a task which finished long before. Bye, bye, productivity!!
 

metadata

@@ -1,8 +1,13 @@
 --- !ruby/object:Gem::Specification 
 name: rakegrowl
 version: !ruby/object:Gem::Version 
+  hash: 17
   prerelease: 
-  version: 0.3.0
+  segments: 
+  - 0
+  - 3
+  - 1
+  version: 0.3.1
 platform: ruby
 authors: 
 - "Sergio Gil P\xC3\xA9rez de la Manga"
@@ -10,20 +15,10 @@ autorequire:
 bindir: bin
 cert_chain: []
 
-date: 2011-05-11 00:00:00 +02:00
+date: 2011-09-21 00:00:00 +02:00
 default_executable: 
-dependencies: 
-- !ruby/object:Gem::Dependency 
-  name: rspec
-  prerelease: false
-  requirement: &id001 !ruby/object:Gem::Requirement 
-    none: false
-    requirements: 
-    - - ~>
-      - !ruby/object:Gem::Version 
-        version: 1.3.0
-  type: :development
-  version_requirements: *id001
+dependencies: []
+
 description: Get Growled when your long running rake tasks finish
 email: sgilperez@gmail.com
 executables: []
@@ -51,12 +46,18 @@ required_ruby_version: !ruby/object:Gem::Requirement
   requirements: 
   - - ">="
     - !ruby/object:Gem::Version 
+      hash: 3
+      segments: 
+      - 0
       version: "0"
 required_rubygems_version: !ruby/object:Gem::Requirement 
   none: false
   requirements: 
   - - ">="
     - !ruby/object:Gem::Version 
+      hash: 3
+      segments: 
+      - 0
       version: "0"
 requirements: []