When I start the Webrick server I get the error messgage…
/config/boot.re.29:Warning: require_gem is obsolete. Use gem instead
Anyone know what this means.
Also, if I rake migrate I get the same message then the command promt
closes and the database does not update.
I’m not sure why rake migrate would be disappearing on you with this.
However, you’ve recently upgraded RubyGems and have not upgrade some
code that still uses require_gem – which is obsolete and will be
removed soon.
Is the “rails” command for generating apps actually producing the code
with
require_gem? Has it not been patched so that RubyGems < 0.9.1 will
still
work? Other wise…
Is the “rails” command for generating apps actually producing the code with
require_gem? Has it not been patched so that RubyGems < 0.9.1 will still
work? Other wise…
$ script/about
./script/…/config/boot.rb:29:Warning: require_gem is obsolete. Use
gem instead.
About your application’s environment
Ruby version 1.8.5 (powerpc-darwin8.8.0)
RubyGems version 0.9.1
Rails version 1.2.1
…
The above is from a MacPorts-installed rails. Locomotive has the same
issue:
$ script/about
./script/…/config/boot.rb:29:Warning: require_gem is obsolete. Use
gem instead.
About your application’s environment
Ruby version 1.8.5 (powerpc-darwin7.9.0)
RubyGems version 0.9.1
Rails version 1.2.1
…
I just ran rake rails:update (per my other post, and thaaanks for
teeelling me about it, guys!), and it fixed my gem() calls by
upgrading them to require_gem().
I just ran rake rails:update (per my other post, and thaaanks for
teeelling me about it, guys!), and it fixed my gem() calls by
upgrading them to require_gem().
Shouldn’t that be the other way 'round?
That was my insinuation. I fixed things manually, like y’all are
discussing, then I ran rails:update, and it un-fixed them.
The base generator is generating the noisily deprecated version.
Oooh, lookie here:
phlip@penbird:~/projects/scratch$ public/dispatch.rb
./public/…/config/boot.rb:29:Warning: require_gem is obsolete. Use
gem instead.
Status: 400 Bad Request
/usr/lib/ruby/gems/1.8/gems/activesupport-1.4.0/lib/active_support/dependencies.rb:405:in to_constant_name': Anonymous modules ha ve no name to be referenced by (ArgumentError) from /usr/lib/ruby/gems/1.8/gems/activesupport-1.4.0/lib/active_support/dependencies.rb:215:in qualified_name_for’
from
/usr/lib/ruby/gems/1.8/gems/activesupport-1.4.0/lib/active_support/dependencies.rb:477:in const_missing' from /usr/lib/ruby/gems/1.8/gems/rails-1.2.1/lib/dispatcher.rb:117:in reset_after_dispatch’
from
/usr/lib/ruby/gems/1.8/gems/rails-1.2.1/lib/dispatcher.rb:51:in
`dispatch’
from public/dispatch.rb:10
A brand-new Rails program has the bug that I’m stuck on, as mentioned
in my other post.
Is the “rails” command for generating apps actually producing the code with
require_gem? Has it not been patched so that RubyGems < 0.9.1 will still
work? Other wise…
I just ran rake rails:update (per my other post, and thaaanks for
teeelling me about it, guys!), and it fixed my gem() calls by
upgrading them to require_gem().
I tried changing require_gem to just gem but the prompt still closed
after running rake migrate. I’ve unistalled and installed instant rails
(I know lazy of me) but this problem has ot resurfaced.
When I start the Webrick server I get the error messgage…
/config/boot.re.29:Warning: require_gem is obsolete. Use gem instead
Anyone know what this means.
Also, if I rake migrate I get the same message then the command promt
closes and the database does not update.
Sorry, hit the wrong button…
Just wanted to add that on my machine (with Ruby Version 1.8.5p12
Installer Version 185-22 - just fresh installed an hour ago) rake
db:migrate crashes commend prompt. I also saw require_gem obsolete
thing, but I think this crashing has little/nothing to with require_gem
even after I got rid of it (manually), it still crashes the command
shell.
I’m not sure why rake migrate would be disappearing on you with this.
However, you’ve recently upgraded RubyGems and have not upgrade some
code that still uses require_gem – which is obsolete and will be
removed soon.
I really hope that’s not true, as a ton of apps use require_gem
including stuff in the latest version of rails. If they remove it
anytime soon stuff is going to break left and right.
run rake with the -t option to get a stack trace.( rake -t db:migrate )
Check your database.yml, that can be a source of silent failure with the
db:migrate task.
I’m not sure why rake migrate would be disappearing on you with this.
However, you’ve recently upgraded RubyGems and have not upgrade some
code that still uses require_gem – which is obsolete and will be
removed soon.
I really hope that’s not true, as a ton of apps use require_gem
including stuff in the latest version of rails. If they remove it
anytime soon stuff is going to break left and right.
Then the current version of rails is broken. require_gem is bad juju.
run rake with the -t option to get a stack trace.( rake -t db:migrate )
Check your database.yml, that can be a source of silent failure with the
db:migrate task.
I experimented a bit with this - here is what it looks like.
rake crashes command prompt anytime - first I thought that it happens
when there is an error. However, it happens EVERY time rake is run.
Below is the result of a successful rake -t db:migrate (piped to a file
the only way to get the output). After it finishes, command shell
disappears.