left the gemspec date as generated previously (by hoe)
... thus latest gem releases show up "weird" old dates
review jdbc- gemspec descriptions and summaries
"better" (Rails-aware) RUBYLIB when running `rake rails:test`
require mocha from tests insteda of from Bundler
thus we avoid a deprecation warning with Mocha 0.13
setup activerecord/test dependencies into a rails group
(based on Rails/ActiveRecord 3.2.9)
unfortunately we need to declared actionpack due session tests
simply adding it into the RUBYLIB (from rails.rake) when running rake rails:test would get a bit complicated since there's a lot of versioned deps for the gem such as rack and others ...
we shall setup the connection methods when adapter is loaded
this is relevant when using the 'jdbcxxx' adapter AR than attempts to require the adapter file and expects a jdbcxxx_connection method to be available on AR::Base

this reverts 20522b6ce39a4a9d9c4aaade461b4480ef5a4ae7
but on the other hand jdbc- gems should get required (for now when establishing the connection) with the possibility to work even when the driver gem is not-available and the .jar is on CP
Merge pull request #288 from kares/master

"fix" incorrect .gemspec (release) dates in jdbc-xxx gems
Merge pull request #289 from kares/rails-tests

setup the connection methods when (jdbc) adapter is loaded
update READMEs / LICENSEs for jdbc driver gems
Update Rakefile to ease building all drivers and adapters

- all namespace now operates on drivers and adapters
- new drivers namespace operates only on drivers
- new adapters namespace operates only on adapters
Don't attempt to load the 1.3.0 unless on at least Java 1.7.
Revert to auto-loading driver jars

We have many clients that expect simply including the jdbc-* gems is
sufficient to ensure the actual JDBC driver is on the classpath.
While we want to move to requiring an intentional load_driver, or
loading the driver when it's actually needed at connection time,
we can't break compatibility in the 1.2.x series.

For now, if you want to explicitly tell the jdbc-* gems to not auto-load
the driver jars, set the Java system property arjdbc.skip.autoload to true.
Update Rakefile to ease building all drivers and adapters

- all namespace now operates on drivers and adapters
- new drivers namespace operates only on drivers
- new adapters namespace operates only on adapters
PostgreSQL connections default to current user

If no username is given in the configuration for a postgresql connection,
default to the currently logged in user (as given by the user.name Java
property).  Closes #257.
Merge pull request #294 from jruby/release_cleanup

Release cleanup
update derby to 10.8.3.0
Merge pull request #295 from kares/derby-10.8.3.0

update derby to 10.8.3.0
do not auto-require the driver + jdbc test needs derby as well
Merge pull request #296 from kares/master

issues running tests locally + should not auto-require the driver gem in tests