– cut here –
~/samples/jruby/typo-5.0.3 >~/testbed/jruby-1.1.2/bin/jruby -S rake
db:migrate
(in /Users/arungupta/samples/jruby/typo-5.0.3)
rake aborted!
no such file to load –
/Users/arungupta/samples/jruby/typo-5.0.3/config/…/vendor/rails/railties/lib/initializer
/Users/arungupta/samples/jruby/typo-5.0.3/rakefile:4:in
`/Users/arungupta/samples/jruby/typo-5.0.3/rakefile’
(See full trace by running task with --trace)
– cut here –
/Users/arungupta/samples/jruby/typo-5.0.3/rakefile:4:in
`/Users/arungupta/samples/jruby/typo-5.0.3/rakefile’
(See full trace by running task with --trace)
– cut here –
Typo 5.0.3 and 5.0.4 doesn’t support Rails 2.1. After discussion with
neuro, Typo support Rails 2.1 in version 5.1. Not before. So the next
release of Typo doesn’t support Rails 2.1. Only 2.0.x
I see this topic was touched on but I figured hey… let’s beat it to
death!
Typically with major version changes of the “Rails” Core, from 2.0 to
2.1, the application needs to be “ported” to the new version.
Depending on the changes this may be easy, or painful.
However, when going from Rails 1.2.3 to Rails 1.2.6, the application
should work with minimal issues; there may be some issues that
undesirable functionality, something not working right. It is the
unfortunate design of Ruby on Rails.
When someone develops an application or creates it with the ‘rails’
command, it’s basically destined for the version of rails that they
have installed. Until said person, or someone else ‘ports’ the
application to Ruby on Rails 2.1 in this case.
Long story short, when an application says it requires Ruby on Rails
2.0.2 or 2.0.3, it’s generally suggested to run with that exact
version to get the optimal results.
This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.