i was able to reproduce with ruby 1.8.7 (2010-01-10 patchlevel 249) [i686-darwin9.8.0]

unpacking the gem in vendor/plugins/ seems to work for me. although, rake call does generate a warning:

DEPRECATION WARNING: Having rake tasks in PLUGIN_PATH/tasks or PLUGIN_PATH/rails/tasks is deprecated. Use to PLUGIN_PATH/lib/tasks instead.

cd vendor/plugins
gem unpack faker

Indeed I came across this problem as well, and it's completely reproducible.

This said, there is an easy workaround, which uses Bundler as is easy.

In your bundle file, declare the following:

    group :rake do
      gem 'faker'
    end

and then add the following to your Rakefile, or even to the top of the individual rake task:

    Bundler.require(:rake)

then all your problems are solved.

If this is inheriting from the :environment task then shouldn't that be the one that's loading these gems? I don't think the rake group workaround is the best idea.

Uh, shouldn't that be inside the :environment task where this inherits from? That would make more sense, no?

Sorry Ryan, I guess I misunderstood you. Can you please give an example?

I am suggesting that this Bundler.require(:rake) be put into task :environment definition rather than in the Rakefile of the application.

It's better to avoid adding bundler inside the framework. We should do our best to have bundler just in the generated application in order to be packaging system agnostic. :)

Ah right, of course, then yes Lenary's suggestion is fine. Sorry for the confusion.

No problem at all!

I'm just about to write a generator patch for this. :D

the problem is machinist require faker..It solve delete(or coment) require 'faker' inside machinist.rb..I had the same problem :).....