On Monday, October 14, 2013 10:52:04 AM UTC-7, GregD wrote: > > I notice the changes to how the jdbc drivers are loaded and I can not get > connected via jdbc anymore. Where or how do I require the jar? CLASSPATH > was how jruby did it before and the code tried the require for various jar > files that ship with different SqlAnywhere releases. From the command line, > how do I require that jar? >
Via the standard ruby methods: jruby -r sajdbc4.jar ... RUBYOPT=-rsajdbc4.jar jruby ... The issue with requiring specific jar names is it requires that they be stored at the root of one of the ruby load paths. These jars can be stored in subdirectories or outside the ruby load path, so Sequel does not require the .jar files automatically (it will require the jdbc-* gem automatically for the subadapters that can be used with jdbc-* gems, since that is just normal gem loading). Thanks, Jeremy -- You received this message because you are subscribed to the Google Groups "sequel-talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sequel-talk. For more options, visit https://groups.google.com/groups/opt_out.
