# Issue with rake and model names that conflict with FileUtil

**URL:** <https://www.ruby-forum.com/t/issue-with-rake-and-model-names-that-conflict-with-fileutil/109359>\
**Category:** Ruby\
**Created:** [July 13, 2007, 7:00pm UTC](https://www.ruby-forum.com/t/issue-with-rake-and-model-names-that-conflict-with-fileutil/109359 "2007-07-13T19:00:09Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![jack](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/j/cc9497/32.png) [@jack](https://www.ruby-forum.com/u/jack)\
**Post date:** [July 13, 2007, 7:00pm UTC](https://www.ruby-forum.com/t/issue-with-rake-and-model-names-that-conflict-with-fileutil/109359/1 "2007-07-13T19:00:09Z")

</div>

Hi all,

I don’t believe this has been discussed here, and its something I’ve run  
into recently. Its a known issue, but I’m wondering if anyone has some  
thoughts on fixing it. Some background information can be found here:

[http://dev.rubyonrails.org/ticket/4953](http://dev.rubyonrails.org/ticket/4953)

It looks like the methods were made to be private somewhat recently, but  
.send gets around that…so, while I can define a method explicitly in  
my  
model to get around this issue, it still doesn’t solve the root of the  
problem. Anyone have any thoughts on this?

Thanks!  
Jack

---

<div class="post-metadata">

**Author:** ![jack](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/j/cc9497/32.png) [@jack](https://www.ruby-forum.com/u/jack)\
**Post date:** [July 14, 2007, 1:31am UTC](https://www.ruby-forum.com/t/issue-with-rake-and-model-names-that-conflict-with-fileutil/109359/2 "2007-07-14T01:31:03Z")

</div>

On 7/13/07, Jack D. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote:

> model to get around this issue, it still doesn’t solve the root of the  
> problem. Anyone have any thoughts on this?

This is classic case of open source ball game. Its a clear case of  
namespace pollution by both rake and ActiveRecord.

First, though I understand Jim’s intentions of making things  
friendlier to the users of rake by importing entire FileUtils into  
Object, but there seems to be a problem here.

Then ActiveRecord makes it worse by importing all methods of rake into  
itself. I do not understand why ActiveRecord is hitting upon a rake  
method, while running a migration.