HikariCP 2.4.8 and 2.5.0 released

[Brett Wooldridge]

HikariCP 2.4.8 and 2.5.0 are now released and available in the Sonatype (maven) repository.

The 2.4.8 release marks the entry into maintenance mode for Java 7 support.  This is reflected by a new artifact name, "HikariCP-java7".  The 2.5.0 release marks the appearance of a Java 8+ artifact, retaining the "HikariCP" artifact name.

Functionally, the 2.4.8 and 2.5.0 artifacts are the same, but will diverge over time.

Java 8 maven dependency:

<dependency>

  <groupId>com.zaxxer</groupId>

  <artifactId>HikariCP</artifactId>

  <version>2.5.0</version>

</dependency>

Java 7 maven dependency:

<dependency>

  <groupId>com.zaxxer</groupId>

  <artifactId>HikariCP-java7</artifactId>

  <version>2.4.8</version>

</dependency>

Changes in 2.4.8 / 2.5.0:

 * Release 2.5.0 marks the start of a Java 8 HikariCP artifact.  The Java 7 artifact is
   now called "HikariCP-java7".

 * Release 2.4.8 marks the start of a Java 7 HikariCP artifact, HikariCP-java7, representing
   support for Java 7 entering maintenance mode.

 * Added Connection.commit() call to the fail-fast initialization for databases that
   automatically start a new Connection in a transaction and throw an exception on close
   if it is not committed.
 
 * feature 694: report if a previously reported leaked connection is returned to the pool

 * issue 689: log a warning if default transaction isolation level cannot be detected.
   This can occur with pseudo-database drivers such as the one for JSonar

 * issue 674: fix regression caused by pull request #450 (overzealous optimisation)

Please report problems to the issue tracker in Github.