We have encountered similar issues. We finally decided not rely on Rails finding any classes declared in a module namespace. We liked the organization that the module namespace provided as our models directory was getting pretty large. So we kept our file structure as is, but removed the namespace. Instead, we explicity "require" the classes in our environment.rb file. For example:
require File.dirname(__FILE__) + '/../app/models/reports/stats_report' require File.dirname(__FILE__) + '/../app/models/reports/standings_report' This is a nasty bug and I hope it gets fixed soon. It's unfortunate Rails does not deal with namespaces properly -- at least I think it's a Rails issue. John -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
