I was really looking forward to the latest beta of RadRails (released on May 15 2007), as it fixed the various "Run all (unit, functional, integration and all) tests" functions that were broken in the stable release. So I installed it as soon as it came out, but quickly discovered that a configuration page (that used to contain executable paths settings) had been removed...
The paths are now all derived from the location of the ruby executable. This places an unnecessary strong requirement on the way Rails and Rake are installed, and breaks as soon as you have a setup that the RadRails people consider "non-standard". This happens to be the case under Ubuntu, a pretty popular Linux distribution, currently ranked no less than #1 on distrowatch.com ;-)
I mentioned the above in
this thread on the Aptana/RadRais forums, and thanks to Chris Williams prompt replies, we could get the problem acknowledged and fixed quickly. So, a fix should already be in CVS, but until it gets released, here is a clean (in the sense that it does not dirty up your
/usr/bin
) workaround under Ubuntu:
cd /usr/local/bin
sudo ln -s /usr/bin/ruby ruby
sudo ln -s /usr/bin/ri ri
sudo ln -s /usr/bin/rdoc rdoc
sudo ln -s /var/lib/gems/1.8/bin/rails rails
sudo ln -s /var/lib/gems/1.8/bin/rake rake
After these symbolic links have been prepared, add a Ruby interpreter (Windows > Preferences > Ruby > Installed Interpreters) with a home directory of
/usr/local
. If things still don't work after that, verify that, in the installed interpreters list, this
/usr/local
one is indeed the one with the check mark.