From: hemant <gethemant@...>
Date: 2007-07-14T08:29:44+09:00
Subject: Re: issue with rake and model names that conflict with FileUtil methods

On 7/13/07, Jack Dempsey <jack.dempsey@gmail.com> wrote:
> 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
>
> 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?
>


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.