rubyonrailsin

"Phil Ostler" <lists@ruby-forum.com> wrote in
message news:7e3f1c8e83517d604d3d7ab7545ffd43@ruby-forum.com...
> I'm currently developing a Rails 2 project that I'd like to migrate
> across to Rail 3. However I'm having real trouble in the first place
> getting Rails 3 to work straight out of the box with a blank project.
>
First a hint. There is a gem named rails3b that somebody in the rails core
team created to pull in the missing dependecies of the Rails gem when using
the rails 3 beta.

Second, Your problem is naming the test application "Rails". That results in
a module named "Rails" that contains your application, but the Rails module
is part of Rails' own namespace.

Thus your config/application.rb is trying to create or re-open a
Rails::Application class that is derived from Rails::Application. I'm not an
expert in that corner of Ruby, but I'm not sure tryingg to have a class
derive from itself could ever be expected to work. Further
Rails::Application is already defined, and it has a different base class, so
ruby has no idea what to do, so it spits out an error and stops.

Try creating a project with a unique name. You should probably find that
works better.

--
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 rubyonrails-talk@googlegroups.com.
To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.