I had a gem (call it foo_bar) which implemented a Bar module. It included and ran fine in my Rails project when I added gem "foo_bar" to the module, but I couldn't get the rake tasks to show when I ran rake -T. After some review, I found that the name of the ruby file that kicked everything off was lib/bar.rb when it should have been lib/foo_bar.rb. Changing the file name to match the name in the gemspec fixed it.
You will want to check your gem to make sure your
require 'bar'
statements are actually
require 'foo_bar'
statements.
Friday, April 5, 2013
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment