I'm guessing the bug was fixed between p72 and p174. As a result, rexml is being pulled in by *Rails* to apply the security patch on p72, but no on p174. So no bug at all.
In general, if you want rexml, you should require it yourself (as opposed to relying on it being a dependency of some other library...) Yehuda Katz Developer | Engine Yard (ph) 718.877.1325 On Tue, Jan 12, 2010 at 2:52 PM, Pito Salas <[email protected]> wrote: > > The trick here is that rexml/document is only required inside this > > conditional (in core_ext/rexml.rb): > > > > unless (defined?(REXML::VERSION) ? REXML::VERSION : REXML::Version) > > > "3.1.7.2" > > > > So I'm guessing the working machine has an earlier patchlevel of Ruby > that > > triggers the fix, and the not-working one obviously has a later version > that > > doesn't. > > > > Working machine: ruby 1.8.7 (2008-08-11 patchlevel 72) > [universal-darwin10.0] > Not working machine: ruby 1.8.7 (2009-06-12 patchlevel 174) [i686-darwin10] > > Indeed. So, is it a bug in Rails, or a bug in Ruby, or a bug in my brain? > > Thanks!! > > - Pito > > -- > You received this message because you are subscribed to the Google Groups > "Ruby on Rails: Core" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<rubyonrails-core%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/rubyonrails-core?hl=en. > > > >--
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to [email protected].
For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.
