On 10/3/07, Glenn Rempe <[EMAIL PROTECTED]> wrote: > > > You may want to also take a look at this bug report that I filed. I > had the same problem and running the 'rake rails:freeze:edge > TAG=rel_2-0-0_PR' TWO times resolved the issue for me when upgrading a > 1.2.3 app. Explanation in the bug report. > > http://dev.rubyonrails.org/ticket/9743
Thanks, Glenn. To everyone: I've been wanting to bring this issue up for a long time now, but always keep forgetting. Everyone knows by now that AWS has been replaced by ActiveResource. This change in framework requirements broke the freeze:edge task for reasons already discussed. The questions I want to bring up are: 1. Are we going to "fix" this in Rails 2.0 Initializer (ie. make it not whine about missing ARes)? 2. 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? 3. 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. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
