Skip to content
Browse files

activerecord-jdbc-adapter does not yet have a rails 3.1 compatible

release. Current bleeding edge version fixes most, but not all
build problems.
  • Loading branch information...
1 parent c506532 commit 8ded749e8e86e21834b2dde00963721cf7c106d4 @kaapa kaapa committed
Showing with 4 additions and 0 deletions.
  1. +2 −0 Gemfile
  2. +2 −0 spec/dummy_app/Gemfile
View
2 Gemfile
@@ -7,6 +7,8 @@ group :development, :test do
gem 'rails', '~> 3.1.0.rc5'
platforms :jruby do
gem 'jruby-openssl', '~> 0.7'
+ # activerecord-jdbc-adapter does not yet have a rails 3.1 compatible release
+ gem 'activerecord-jdbc-adapter', :git => 'https://github.com/nicksieger/activerecord-jdbc-adapter.git'
case ENV['CI_DB_ADAPTER']
when 'mysql'
gem 'activerecord-jdbcmysql-adapter', '~> 1.1', :platform => :jruby
View
2 spec/dummy_app/Gemfile
@@ -9,6 +9,8 @@ gem 'paperclip', '~> 2.3.11'
group :development, :test do
platforms :jruby do
gem 'jruby-openssl', '~> 0.7'
+ # activerecord-jdbc-adapter does not yet have a rails 3.1 compatible release
+ gem 'activerecord-jdbc-adapter', :git => 'https://github.com/nicksieger/activerecord-jdbc-adapter.git'
case ENV['CI_DB_ADAPTER']
when 'mysql'
gem 'activerecord-jdbcmysql-adapter', '~> 1.1', :platform => :jruby

8 comments on commit 8ded749

@kaapa
Collaborator

@sferik: Or should we just drop jRuby from test suite until activerecord-jdbc-adapter is on par with Rails 3.1 AR api? Using latest results in 26 failures which I believe are all due to adapter incompatibly.

@sferik
Owner

I'm okay with dropping JRuby support until activerecord-jdbc-adapter has been updated. Does that mean we can officially switch over to using Travis as our primary CI?

@kaapa
Collaborator

I think we should do that!

@sferik
Owner

Okay, feel free to spin down the Hudson server.

I'll make http://ci.railsadmin.org redirect to http://travis-ci.org/sferik/rails_admin

@sferik
Owner

Okay, I switched over the DNS.

@sferik
Owner

@kaapa I just looked at http://demo.railsadmin.org/admin and noticed images were broken. Can we fix that?

@kaapa
Collaborator

Yep, I was in the middle of upgrading demo to 3.1, but I'm leaving that to another day - set it to point to our rails-3.0 branch. Now works again.

@bbenezech
Collaborator

@kaapa can you migrate quickly? The demo is quite broken, a lot of JS stuff looks outdated.

Please sign in to comment.
Something went wrong with that request. Please try again.