I noticed section "Gemfile" under "Upgrading from Rails 3.2 to Rails 4.0" in guides/source/upgrading_ruby_on_rails.md, which indicates that the assets group needs to be removed from my Gemfile when upgrading from 3.2 to 4.0. I was trying to find more information on what I'm supposed to do with the entries in that group (i.e. sass-rails, coffee-rails, therubyracer, and uglifier), so I went and looked in guides/source/asset_pipeline.md. As far as I can figure out, the "Upgrading from Old Versions of Rails" section still refers to the procedures for upgrading from 3.0 to 3.1 (although it isn't very explicit about it). It includes instructions to include an assets group in the Gemfile, which is in direct contradiction to the instructions in the upgrade guide! I'm still trying to figure out the appropriate course of action, so I doubt I know enough to authoritatively update the documentation, but I probably won't be the only confused user!
Yep, I emailed @guilleiguaran about this yesterday.
To answer your question, "Just put them in the gemfile without a group", but we need to document this better.
Thank you guys for report this, I will try to get the asset pipeline docs updated this weekend.
If one is using asset precompilation, can one put them in just the development and test groups? Or has the whole precompilation thing changed?
My understanding (I think it was @rubys that said this) is that you precompile in the production env. So they're in everything.