I had figured the problem was something like that, and I think it highlights a bigger issue: These types of errors are not uncommon, yet the error messages are uninformative, and the solutions are not officially documented. It would seem that require_or_load, require_dependency and require_association are all meant for internal use only, yet there seem to be situations where using them is the only way to make things work.
Any ideas on how to tackle this? On 21-Sep-09, at 5:09 PM, Luke wrote: > I found the solution, at least in my case. I have a class defined in > test/mock/development that uses 'require' vs. 'require_dependency'. > Changing to require_dependency fixed the problem, which I can > understand. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" 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-core?hl=en -~----------~----~----~----~------~----~------~--~---
