This project is archived and is in readonly mode.
gem dependency unable to load unpacked gem when version doesn't match exactly
Reported by Pedro Belo | August 2nd, 2008 @ 01:05 AM | in 2.x
When using config.gem, if you specify a version requirement like '>=1.0.0' Rails will only load unpacked gems with this exact version. Newer gems are not loaded; so if you have the version 1.1 of this gem in your vendor Rails won't load it.
Attached is a patch to make gem_dependency load any gem on vendor that matches the gem requirement.
Comments and changes to this ticket
-
Matt Jones November 13th, 2008 @ 01:51 AM
- Tag changed from “2.1, patch” to “2.1, patch, railties”
This is fixed in the 2.2RC - see #1128.
-
Michael Koziarski November 13th, 2008 @ 10:39 AM
- State changed from “new” to “duplicate”
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
<h2 style="font-size: 14px">Tickets have moved to Github</h2>
The new ticket tracker is available at <a href="https://github.com/rails/rails/issues">https://github.com/rails/rails/issues</a>
People watching this ticket
Matt Jones
Michael Koziarski
Pedro Belo
Attachments
Referenced by
-
1128
Fix config.gem bugs and add more tests
incorporates, via using the gem loader for frozen gems, f...