Option #1: Use the gem as a plugin instead. Files that match the following pattern are automatically pulled in, so you’re good to go:

"#{RAILS_ROOT}/vendor/plugins/*/**/tasks/**/*.rake"

Option #2: Create a ruby file that loads the gem’s tasks, then require the ruby file you made in your rail app’s Rakefile.  For example, if you’ve installed the Facebooker gem and you want to use its rake tasks, you might create a file called ‘facebooker.rb’ and save it to your <railsapproot>/tasks directory with these contents:

$VERBOSE = nil
Dir["#{Gem.searcher.find('facebooker').full_gem_path}/lib/tasks/*.rake"].each { |ext| load ext }

Then add this line to your Rakefile:

require 'tasks/facebooker'

But as it turns out, Facebooker’s tasks uses relative paths to get at its config file in your rails app, which won’t work if its installed in the gem path as a gem rather than in your rails app as a plugin! So be careful with using option #2, it may not be what the gem you’re trying to use expects.