Actually, that probably would be ideal...DHH seems fond of the idea of JRuby on Rails, so perhaps it would not be a difficult matter to get our adapter included in Rails proper.On 6/8/06,
Thomas E Enebo <[EMAIL PROTECTED]> wrote:
Could it not also get submitted to Rails directly? It would be ni
Could it not also get submitted to Rails directly? It would be nice
if people using JRuby did not need a seperate install. I think most
connection adapters are distributed as part of activerecord.
-Tom
On Wed, 07 Jun 2006, Charles O Nutter defenestrated me:
>
>Whatever is the typical w
Whatever is the typical way to release ActiveRecord adapters, I'm all for. I know some aspects of Rails are gems, and it's nicely automated, but perhaps plugins are too. I really need to start reading my AWDWR book more.
On 6/7/06, Nick Sieger <[EMAIL PROTECTED]> wrote:
On 6/7/06, Charles O Nutter
On 6/7/06, Charles O Nutter <[EMAIL PROTECTED]> wrote:
A thought on one aspect of where to put Rails stuff:Nick, I think it would make sense if the ActiveRecord-JDBC connector was installable as a Gem. It could just live on RubyForge and perhaps eventually just be included in Rails (if we can keep
A thought on one aspect of where to put Rails stuff:Nick, I think it would make sense if the ActiveRecord-JDBC connector was installable as a Gem. It could just live on RubyForge and perhaps eventually just be included in Rails (if we can keep it small and make it general-purpose, (mostly) DB-agnos
