That is a shame. Not everyone likes Rails… or ActiveRecord… It’s a
matter of taste, but the real problem here is using “JRuby” as a synonym
for ‘JRuby on Rails’. They are not the same, and we should be very
careful to use proper terminology in the changelog for new releases.
Please don’t take this as a whine, because I am a huge fan of the work
you are doing, Nick, and of the whole team. JRuby is definitely the
future of easy non-Rails R. deployments (because there is no mod_ruby,
only mod_rails). It seems that some improvements are going backwards,
from Rails-specific to Ruby-general, and I don’t like seeing that.
But I’ll take it as it comes and keep chipping away at getting Waves to
run on JRuby (note, we currently use Sequel and SQLite in the default
config, so a new version of AR is not going to help much in this
Thanks for all the great work guys!
— On Mon, 6/2/08, Nick S. <[email protected]> wrote:
From: Nick S. <[email protected]>
Subject: Re: [jruby-user] sqlite3 in JRuby 1.1.2
To: [email protected]
Date: Monday, June 2, 2008, 7:12 AM
On Sun, Jun 1, 2008 at 10:30 PM, rob08 <[email protected]>
> I notice that the new release adds support for Sqlite3: “JRUBY-2438
> SQLite3 using JRuby”
> I’ve tried a few things but can’t seem to get this working. Has
> some step-by-step instructions?
Sorry, this is actually in activerecord-jdbc-adapter, not JRuby
proper. Expect a new ar-jdbc release soon, sorry for the delay!
To unsubscribe from this list, please visit: