Yes it works, but on OSX there's a potential Java hitch to be aware of. Download "Eclipse Ganymede 3.4":http://www.eclipse.org/downloads/. Unzip Eclipse to a directory (normally Applications). Download "Flex Builder 3.01 Plugin":https://www.adobe.com/cfusion/tdrc/index.cfm?loc=en_us&product=flex_eclipse. *BEFORE* you run the Flex Builder Plugin installer on OSX, check that your java version is set to 1.5. However a simple @java -version@ is not enough to satisfy the installer. You also have to @cd /System/Library/Frameworks/JavaVM.framework/Versions/@ and @ls -al@ to check that CurrentJDK -> 1.5.0. I'd previously installed Java 1.6 on Mac, and although @java -version@ gave me 1.5, the CurrentJDK -> 1.6.0. This seems to have caused my install to fail with the error: 'This installation can still be configured manually as a Product Extension' and soon after an alert with 'a newer file named "com.adobe.flexbuilder.debug.e33_3.0.205647.jar" already exists at "/Applications/Adobe Flex Builder 3 Plug-in/eclipse/plugins" Do you want to overwrite this file?' Trying to follow the instructions offered is a fruitless exercise I won't bother recounting because "someone else already has":http://www.newviewnetworks.com/nvnhome/blog/client/?p=103 (Borg - no permalinks for comments on that site). Anyway ensuring you have 1.5.0 all the way should guarantee a successful install. 2008-11-18T16:45:27Z 0 25 flex-builder-3-01-plugin-in-eclipse-ganymede-3-4-on-osx 2008-11-18T17:06:09Z One of the nice things about rails 2 is the gem dependencies you can express in your environment.rb file: <code lang="ruby"> Rails::Initializer.run do |config| config.gem 'mislav-will_paginate', :version => '~> 2.2.3', :lib => 'will_paginate', :source => 'http://gems.github.com' end </code> By expressing dependencies within the application's environment file, you can then run @rake gems:install@ on a target machine and it will install all the required gems. However, because I use Rspec in development, running any sort of rake command on my project folder on the server failed with @no such file to load -- spec/rake/spectask@. This is because the rakefile itself has a dependancy on rspec - a little problematic. On installing the rspec gem on my server, I was hit with a bunch of missing dependencies: @Could not find RubyGem diff-lcs (>= 0)@, @Could not find RubyGem spicycode-rcov (>= 0.8.1.3)@, @Could not find RubyGem syntax (>= 0)@, and @Could not find RubyGem hoe (>= 1.8.0)@. After installing these gems rake -T finally worked again. It seems this is all caused by the "wonky dependencies":http://merb.lighthouseapp.com/projects/7433/tickets/603-merb-gen-complains-about-spicycode-rcov of the latest Rspec. Not so much fun. 2008-10-21T21:11:47Z 0 18 rspec-1-1-9-not-so-much-fun 2008-10-22T08:29:01Z "RubyAMF":http://code.google.com/p/rubyamf/ gives you @render :amf@ so you can send controller responses as binary AMF streams to Flash applications (also known as Flash remoting). Unfortunately for those Rspec users out there, adding RubyAMF as a plugin results in your previously fine Rspec tests breaking with messages like: "ArgumentError in 'ProjectsController responding to PUT update with invalid params should re-render the 'edit' template' wrong number of arguments (2 for 1)" Someone else "came across this":http://www.mail-archive.com/rspec-users@rubyforge.org/msg02556.html a year ago but the problem still remains (a bug has been filed at Google code). However I can confirm the proposed fix still works. On OSX, I had to modify line 216 in @/usr/local/lib/ruby/gems/1.8/gems/rspec-rails-1.1.8/lib/spec/rails/example/controller_example_group.rb@ to remove the second argument: @deprecated_status_or_extra_options@ 2008-10-12T16:38:16Z 2 15 rubyamf-currently-breaks-rspec-tests 2008-10-22T08:31:12Z With the power of @script/generate rspec_scaffold@ in hand I generated the test scaffold for my Post model. I also got clued up on using the "spec command":http://rspec.info/documentation/tools/spec.html to execute all the tests within a directory. However as expected things didn't go so smoothly. When attempting to run spec I received the message "Your RSpec on Rails plugin is incompatible with your installed RSpec." I executed script/spec instead, which went a bit further but warned me about the MySQL library I was using, so I attempted to @sudo gem install mysql@ which spat out "ERROR: Error installing mysql: ERROR: Failed to build gem native extension." So @sudo gem install mysql -- --with-mysql-config@ worked better, and then I just @rake db:test:clone@ to get the test db sorted. Not being able to run spec bugged me, and a quick Google led me to a "very useful post":http://blog.insoshi.com/2008/07/03/a-rails-21-case-study-upgrading-the-insoshi-social-networking-platform/ which guided me through updating to the latest rspec plugin and gem. So now all the tests run, but with errors that seem to be fixable by modifying the default scaffold code to reflect how my classes are actually structured. 2008-09-16T22:46:39Z 0 5 rspec-in-take-two 2008-10-04T23:19:41Z