Allow dumping the schema even if there aren't any migrations to run.

[nirvdrum]

No description provided.

[JonathanTron]

Thanks, this is a great refactor and new functionality. Could you check the specs failures and see if you can fix them?

[nirvdrum]

Yeah, I'll take care of that. Travis runs a lot more tests than I'm configured to run locally.

[nirvdrum]

@JonathanTron Any tips on getting the JRuby 1.8 tests to run locally? I tried copying over the ci Gemfile for it, but I must be missing the correct version of rspec or something. I'm seeing:

NameError: uninitialized constant Combustion
    const_missing at org/jruby/RubyModule.java:2684
    const_missing at /home/nirvdrum/.rbenv/versions/jruby-1.7.5/lib/ruby/gems/shared/gems/rspec-core-2.14.5/lib/rspec/core/backward_compatibility.rb:14

[nirvdrum]

Well, I audited each change to work out what wasn't 1.8 compatible. So that's fixed, but it'd be helpful to understand how I should be running those specs locally.

[JonathanTron]

@nirvdrum thanks for the fix, here's how you can run the spec under JRuby 1.8 mode:

SEQUEL="~> 3.28.0" BUNDLE_GEMFILE=ci/rails-3.2.gemfile jruby --1.8 -S bundle
SEQUEL="~> 3.28.0" BUNDLE_GEMFILE=ci/rails-3.2.gemfile jruby --1.8 -S rake spec

adapt the SEQUEL environment variable to match a specific version if you want. By default rake spec will run the spec for Postgres only.

[nirvdrum]

Thanks. Just to be sure though, what version of rspec should be used? It's not specified in the Gemfile.

[JonathanTron]

It should work with any RSpec version "~> 2.7.0" (it's defined in the gemspec, which is used by the Gemfile(s))

[nirvdrum]

Gotcha. I think because I wasn't running through bundle exec, it was just picking up whatever I had. And my attempt at copying over the Gemfile made the gemspec part not work. Thanks again.

[JonathanTron]

You're welcome, thanks for taking the time to report your experience and provide fixes.