retroactive_module_inclusion 1.0.2 → 1.0.3

data/History.rdoc

@@ -1,3 +1,9 @@
+=== 1.0.3 / 2011-01-20
+
+* 1 minor enhancement
+
+  * more concise Stats implementation, minor gem description and doc improvements
+
 === 1.0.1 / 2011-01-20
 
 * 1 minor enhancement

data/Rakefile

@@ -8,7 +8,7 @@ require 'hoe'
 Hoe.spec 'retroactive_module_inclusion' do
   developer('Adriano Mitre', 'adriano.mitre@gmail.com')
   
-  self.version = '1.0.2'
+  self.version = '1.0.3'
 
   self.readme_file = 'README.rdoc'
   self.history_file = 'History.rdoc'

metadata

@@ -1,12 +1,13 @@
 --- !ruby/object:Gem::Specification 
 name: retroactive_module_inclusion
 version: !ruby/object:Gem::Version 
-  prerelease: false
+  hash: 17
+  prerelease: 
   segments: 
   - 1
   - 0
-  - 2
-  version: 1.0.2
+  - 3
+  version: 1.0.3
 platform: ruby
 authors: 
 - Adriano Mitre
@@ -46,6 +47,7 @@ dependencies:
     requirements: 
     - - ">="
       - !ruby/object:Gem::Version 
+        hash: 47
         segments: 
         - 2
         - 8
@@ -95,6 +97,7 @@ required_ruby_version: !ruby/object:Gem::Requirement
   requirements: 
   - - ">="
     - !ruby/object:Gem::Version 
+      hash: 3
       segments: 
       - 0
       version: "0"
@@ -103,13 +106,14 @@ required_rubygems_version: !ruby/object:Gem::Requirement
   requirements: 
   - - ">="
     - !ruby/object:Gem::Version 
+      hash: 3
       segments: 
       - 0
       version: "0"
 requirements: []
 
 rubyforge_project: retroactive_module_inclusion
-rubygems_version: 1.3.7
+rubygems_version: 1.4.1
 signing_key: 
 specification_version: 3
 summary: This gem circumvents the "dynamic module include" (aka "double inclusion") problem, which is the fact that M.module_eval { include N } does not make the methods of module N available to modules and classes which had included module M beforehand, only to the ones that include it thereafter