Contribution notes.
Update README.md
Update README.md
Update README.md
Update README.md
Remove Oracle Java 7 requirement, OpenJDK is also fine.
Update README.md
Fixed a bug in HikariConfig.setConnectionTimeout(long) that was causing 0 not to
be infinite.
Merge pull request #14 from NosBit/dev

Fixed a bug in HikariConfig.setConnectionTimeout(long)
Resolved#16 if auto-commit is disabled when the connection is returned then rollback() will be called automatically.
Updates changes file
Fixes #17 add ability to set log writer on datasource either programatically on the datasource or through the HikariConfig.
Update changes file.
Fixed #18 Allow specifying a default transaction isolation level.
Start adding shutdown sematic.
Update changes file.
Merge branch 'dev'

* dev: (23 commits)
  Update changes file.
  Start adding shutdown sematic.
  Fixed #18 Allow specifying a default transaction isolation level.
  Update changes file.
  Fixes #17 add ability to set log writer on datasource either programatically on the datasource or through the HikariConfig.
  Updates changes file
  Resolved#16 if auto-commit is disabled when the connection is returned then rollback() will be called automatically.
  Fixed a bug in HikariConfig.setConnectionTimeout(long) that was causing 0 not to be infinite.
  Add debug logging.
  Merged changes from ams2990
  Added a constructor for HikariConfig that accepts a Properties object. Modified props-file reading constructor to use try-with-resources to ensure prompt file close.
  More code size reduction for inlining.
  Remove unnecessary null checks
  Use the configured temp folder for dumping instrumented class files in debug mode.
  Remove codex from agent jar.
  Trigger the background pool fill at a fixed delay after exiting getConnection().
  Add test for connection use after close().
  Switch _isClosed volatile boolean to a ThreadLocal instead.  This allows us to handle the case where a consumer tries to continue to use a connection after it has been returned to the pool and dispatched to another consumer.  Previously, when the new consumer received the connection, the _isClosed boolean would be reset, allowing an old consumer to invoke against it without error.  Now due to the ThreadLocal, and old consumer will still continue to see the connection as being in the closed state, even when it has become “unclosed” for another consumer.
  Remove redundant (duplicate) __init() call injected into constructors.
  Set debug level to line numbers only.
  ...
[maven-release-plugin] prepare release HikariCP-1.2.2
[maven-release-plugin] prepare for next development iteration
Update README.md