Forum: Ruby on Rails rake gems broken when using capistrano-ext in rails 2.2.x

Announcement (2017-05-07): www.ruby-forum.com is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see rubyonrails.org/community and ruby-lang.org/en/community for other Rails- und Ruby-related community platforms.
Freddy A. (Guest)
on 2008-12-04 06:09
(Received via mailing list)
Just tested the rails bort setup and got an error when running rake
gems:

 - [F] capistrano-ext
rake aborted!
You have a nil object when you didn't expect it!
The error occurred while evaluating nil.dependencies

If I change to rails 2.1.2 it works fine but any of the rails 2.2.x
versions gives the same nil...
The problem line is => config.gem "capistrano-ext", :lib =>
"capistrano"

Anyone else seen this?

Here is the full trace:

 - [F] capistrano-ext
rake aborted!
You have a nil object when you didn't expect it!
The error occurred while evaluating nil.dependencies
/opt/local/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/rails/
gem_dependency.rb:77:in `dependencies'
/opt/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
`to_proc'
/opt/local/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/rails/
gem_dependency.rb:80:in `map'
/opt/local/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/rails/
gem_dependency.rb:80:in `dependencies'
/opt/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
`to_proc'
/opt/local/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/rails/
gem_dependency.rb:80:in `map'
/opt/local/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/rails/
gem_dependency.rb:80:in `dependencies'
/opt/local/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/tasks/gems.rake:
15:in `print_gem_status'
/opt/local/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/tasks/gems.rake:4
/opt/local/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/tasks/gems.rake:3:in
`each'
/opt/local/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/tasks/gems.rake:3
/Users/freddy/.gem/ruby/1.8/gems/rake-0.8.3/lib/rake.rb:617:in `call'
/Users/freddy/.gem/ruby/1.8/gems/rake-0.8.3/lib/rake.rb:617:in
`execute'
/Users/freddy/.gem/ruby/1.8/gems/rake-0.8.3/lib/rake.rb:612:in `each'
/Users/freddy/.gem/ruby/1.8/gems/rake-0.8.3/lib/rake.rb:612:in
`execute'
/Users/freddy/.gem/ruby/1.8/gems/rake-0.8.3/lib/rake.rb:578:in
`invoke_with_call_chain'
/opt/local/lib/ruby/1.8/monitor.rb:242:in `synchronize'
/Users/freddy/.gem/ruby/1.8/gems/rake-0.8.3/lib/rake.rb:571:in
`invoke_with_call_chain'
/Users/freddy/.gem/ruby/1.8/gems/rake-0.8.3/lib/rake.rb:564:in
`invoke'
/Users/freddy/.gem/ruby/1.8/gems/rake-0.8.3/lib/rake.rb:2019:in
`invoke_task'
/Users/freddy/.gem/ruby/1.8/gems/rake-0.8.3/lib/rake.rb:1997:in
`top_level'
/Users/freddy/.gem/ruby/1.8/gems/rake-0.8.3/lib/rake.rb:1997:in `each'
/Users/freddy/.gem/ruby/1.8/gems/rake-0.8.3/lib/rake.rb:1997:in
`top_level'
/Users/freddy/.gem/ruby/1.8/gems/rake-0.8.3/lib/rake.rb:2036:in
`standard_exception_handling'
/Users/freddy/.gem/ruby/1.8/gems/rake-0.8.3/lib/rake.rb:1991:in
`top_level'
/Users/freddy/.gem/ruby/1.8/gems/rake-0.8.3/lib/rake.rb:1970:in `run'
/Users/freddy/.gem/ruby/1.8/gems/rake-0.8.3/lib/rake.rb:2036:in
`standard_exception_handling'
/Users/freddy/.gem/ruby/1.8/gems/rake-0.8.3/lib/rake.rb:1967:in `run'
/Users/freddy/.gem/ruby/1.8/gems/rake-0.8.3/bin/rake:31
/usr/bin/rake:19:in `load'
/usr/bin/rake:19
Freddy A. (Guest)
on 2008-12-04 06:22
(Received via mailing list)
Found it... There was a bug that was found and will be fixed in Rails
2.2.3... The patch at lighthouse is here:

http://rails.lighthouseapp.com/projects/8994-ruby-...
This topic is locked and can not be replied to.