Remove jeweler from gemspec and remove version constraint from jeweler i...

[unclebilly]

bundle update is not working on a fresh checkout of the repo because of a version conflict between bundler and jeweler:

~/workspace/oracle-enhanced $ bundle
Fetching gem metadata from http://rubygems.org/.......
Fetching gem metadata from http://rubygems.org/..
Resolving dependencies...
Bundler could not find compatible versions for gem "bundler":
  In Gemfile:
    jeweler (~> 1.5.1) ruby depends on
      bundler (~> 1.0.0) ruby

  Current Bundler version:
    bundler (1.3.0)

This Gemfile requires a different version of Bundler.
Perhaps you need to update Bundler by running `gem install bundler`?

This commit gets bundle working again by removing the version constraint on jeweler from the Gemfile. It also removes jeweler from the gemspec (it is unnecessary there).

[yahonda]

Thanks for the pull request. Since current oracle enhanced adapter supports from Rails 2.3 to Rails 3.2. Does this commit work for all versions?

[unclebilly]

@yahonda The jeweler gem is used for managing and releasing gems. It should not be included in the gemspec as a dependency because the adapter does not depend on it to function. It should remain in the Gemfile under the development section if you guys choose to use it for building and deploying the gem. I did test bundle after making this change, and it worked ok.

[yahonda]

Thanks for the explanation. It looks make sense to me. @rsim @ebeigarts Any ideas?

[rsim]

jeweler gem should be updated to latest version that is compatible with latest bundler and in Gemfile this latest version should be specified.

But it should not be removed from gemspec - currently gemspec is generated by jeweler and it is listing itself as development dependency and not runtime (see rubygems version check in generated gemspec).

[unclebilly]

I restored jeweler in the gemspec and added a version declaration of ~> 1.8, which gets bundle working again.