This project is archived and is in readonly mode.
Vendored Gems Not Being Activated With Rake Tasks
-
Matt Jones
- Assigned user set to Matt Jones
It would be more descriptive to run Rails::GemDependency.add_frozen_gem_paths directly, as that's whats accomplished here. Calling add_gem_load_paths implies that config.gem stuff is getting loaded, which is not the case.
I'm curious, however, how you encountered this error. What gems are you using, and do you have 'require' and/or 'gem' statements in your rake tasks?
-
John Dzak
Ah cool, thanks.
So we encounter this error when a rake tasks in our rails project loads another task which is housed in a gem we wrote. That task eventually calls require 'activesupport' and that is where we encounter the problem.
BTW, this will only happen if the 2.3.1 gems that are vendored are not installed in rubygems. We noticed the problem on a machine that only had the 2.2.2 gems installed.
-
Matt Jones
Does add_frozen_gem_paths solve the problem? 2.3 is right around the corner, and it would be good to get a patch in.
-
John Dzak
Yep, working on the patch right now.
-
John Dzak
Here's the patch.
-
John Dzak
Ooops, scratch that last patch. Picked up the wrong file.
-
Repository
- State changed from new to resolved
(from [9d906707bea997016fd370e33e12dbc21cfcc531]) Vendored gem paths now being loaded if they exist [#2204 Vendored Gems Not Being Activated With Rake Tasks state:resolved]
Signed-off-by: Pratik Naik pratiknaik@gmail.com http://github.com/rails/rails/co...
