gem version pins are preventing use in Rails 3.2

[ijcd]

These are making the gem hard to install (I have a gem that depends on SuperModel). I think it should work if we upgrade, but it seems there are a lot of tests that need to be written to confirm this, eh?

if s.respond_to? :specification_version then
current_version = Gem::Specification::CURRENT_SPECIFICATION_VERSION
s.specification_version = 3

if Gem::Version.new(Gem::VERSION) >= Gem::Version.new('1.2.0') then
  s.add_runtime_dependency(%q<activemodel>, [">= 3.0.0"])
else
  s.add_dependency(%q<activemodel>, ["~> 3.0.0"])
end

else
s.add_dependency(%q, ["~> 3.0.0"])
end

[maccman]

Pull requests always welcome.

[ijcd]

Ok, good to know. I'll share what I come up with. I got trapped under this pin and couldn't tell how active the project was.

[jeffshantz]

A pull request was submitted in #23 7 months ago. :)

[quarklemotion]

#23 was merged a while back, so this issue can be closed