You can clone with
HTTPS or Subversion.
pg 0.18 not support Ruby < 1.9.3
Only use old i18n when version is not compatible
Remove hard dependency on test-unit
Instead show a error message asking users to add the gem to their
Gemfile if test-unit could not be loaded.
Lock i18n to a version that works with Ruby 1.8
Use a version of execjs compatible with Ruby 1.8
Fix broken tests of the previous release
Remove git dependecy
nokogiri >= 1.6 doesn't work with ruby 1.8
Using latest AR-JDBC for JRuby
1.2.5 and 1.2.6 are bad ones
Skip ruby-prof in Gemfile for Ruby 2.0
Update mocha version to 0.13.0 and change requires
Lock mocha in ~> 0.12.x until we fix the Ruby 1.8.7 issues with 0.13.0
Removing JSON for other ruby
It's only required for 1.8 and for JRuby!
I was fixing a bug with JSON pure on 1.8.7
and I found that we have included json for other
1.8 > rubies also.
Use benchmark/ips to measure AR performance
This means we can more easily compare numbers, and we don't have to
specify a single N for all reports, which previously meant that some
tests were running many more/fewer iterations than necessary.
Reason:- 0.12.0 introduced a bug where you got a exception
which is now in 0.12.1 is a warning only!
Ruby-Prof works with ruby-1.9.3 also.
Update performance profiler to work with latest ruby-prof
Thanks to @carlosantoniodasilva
locking ruby-prof until we got a fix
work against 1-0-stable until a new journey is released
Revert "use pg 0.11.0 under ruby 1.8.7"
There's a new pg release, no need for this anymore
This reverts commit 0b5cda7.
use pg 0.11.0 under ruby 1.8.7
removes Ruby constraint in RedCloth dependency
updating arel and journey dependencies
let sdoc say which version of rdoc we depend on
Make quotes in Gemfile consistent (use single quotes)
Use HTTPS rubygems source
Remove rb-fsevent from Gemfile.
use our own fork of sdoc while Vijay's fix is not applied to voloko/sdoc
Enable postgres on the CI
allow people to set a local .Gemfile so that things like ruby-debug a…
…re not required for regular development
bundler treats trunk ruby as ruby 1.9, hack around that for now
Allow to use ruby-debug in 1.9.3
Add ActiveRecord::Relation#uniq for toggling DISTINCT in the SQL query