title: Why do Rails /lib modules prevent gem modules from loading?
body: <p>The title of this question may need renaming. Any suggestions?</p>
  
  <p>In my Rails application there was an old Module in the /lib folder called foo_blaster.rb. I then installed my gem named foo_blaster.rb. None of the code in the gem executed until I deleted the original FooBlaster module. Why is this? Shouldn't Ruby combine the two Modules?</p>
  
  <p>The Modules are the same</p>
  
  <pre><code># lib/foo_blaster.rb
  module FooBlaster
    class Characters
      puts "some characters"
    end
  end
  
  # foo_blaster gem files
  module FooBlaster
     class Users
     end
  end
  
  FooBlaster::Characters #=&gt; some characters
  FooBlaster::Users #=&gt; NameError: uninitialized constant FooBlaster::Users
  </code></pre>
  
  <p>What am I missing here?  </p>
  
  <p>Rails 2.3.18,
  Ruby 1.8.7-p358</p>