> Are we going to "fix" this in Rails 2.0 Initializer (ie. make it not whine > about missing ARes)?
This seems reasonable, it will at least stop hurting people when we next release from trunk. > If the Initializer is not going to change, should we be telling users that > the preferred way of fixing this issue is running the freeze task twice? Running a freeze from 1.2.4 will get the right components. Unfortunately 2.0PR1 landed before 1.2.4 did. > Are we going to do something about this for the future (however unlikely > changing the frameworks again might be)?It's a shame that this error message > is so daunting and misleading. I feel sorry for all those people already > wasting hours trying to figure out what is wrong. If we'd pushed 1.2.4 before 2.0pr1 then user's would have had a safe upgrade which pointed out a few of these things. I think that's a safe approach for the future, unless I'm missing something. -- Cheers Koz --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
