title: Resolving Namespace conflicts between a class and a gem
body: <p>In my Rails 2.3 app, I found that the problem emanates from namespace collisions between an existing ActiveRecord model and a gem I recently added. </p>
  
  <p>Specifically, I was trying to add <code>jammit</code> support to the app. One of jammit's dependant gems require's <code>'platform'</code>, which introduces a <code>Platform</code> <strong>module</strong> into the app's namespace. However, I already have an AR <strong>class</strong> with that name, and renaming it will introduce a lot of additional work and possible bugs. </p>
  
  <p>I was wondering if there's a relatively simple way (using ruby's metamagic or whatnot) to prevent this namespace collision without having to rename my class or alter the actual gem. Thanks.</p>
  
  <h2>EDIT:</h2>
  
  <p>Instead of renaming/wrapping the <strong>class</strong> <code>Platform</code> throughout my app, and since the <strong>module</strong> <code>Platform</code> is only required by one other gem, I resulted to forking both gems, renaming <code>Platform</code> to <code>XPlatform</code> (both for the original gem and the one that imports it), and rebuilding them both. That seemed to work [sigh].</p>