Its Me
1/25/2005 1:54:00 AM
"Jim Weirich" <jim@weirichhouse.org> wrote
> Since the file is evaluated twice, each task action is added to the task
> twice. Therefore running any task executes the actions twice.
>
> Hope this helps.
Very clear now, thanks.
> If there is stuff in the rakefile that the other file depends on, it is
better
> to extract it into a normal library file and let both the rakefile and the
> other file require that third file.
I have had trouble previously before because of the number of Dir and/or
FileUtil methods 'included' by rake. Specifically name conflicts since
whatever rake includes goes into Object, and that conflicted with things I
do in my own code. I was wondering if there was a way around that global
'include', since uses of the Dir or FileUtil methods are (should be?)
limited to within tasks. For example, Tasks could catch missing methods that
are in the set of FileUtil.instance_methods, and handle them appropriately.
Feasible? Worth considering?