HikariCP 2.0.1 released

[Brett Wooldridge]

HikariCP 2.0.1 has been released and the artifacts published to the Maven Central Repository.

IMPORTANT:

Starting with release 2.0.1 the HikariCP project now publishes two artifacts.  One for Java 6/7 and one for Java 8.  The artifact that users have previously used, "HikariCP", is now the Java 8 artifact.  Over time as users move to Java 8 we expect this to be the primary artifact.  Users needing the Java 6/7 compatible artifact should now use artifact named "HikariCP-java6".

 

Java 8 example:

  <dependency>
     <groupId>com.zaxxer</groupId>
     <artifactId>HikariCP</artifactId>
     <version>2.0.1</version>
     <scope>compile</scope>
  </dependency>

Java 6/7 example:
  <dependency>
     <groupId>com.zaxxer</groupId>
     <artifactId>HikariCP-java6</artifactId>
     <version>2.0.1</version>
     <scope>compile</scope>
  </dependency>

Changes between 1.4.0 and 2.0.1

 * Split project into Java 6/7 and Java 8 components.

 * Fixed issue in JNDI object factory which would not allow JNDI-defined
   DataSource properties to pass-thru to the pool.

 * Fixed issue where under certain conditions getConnection() could
   timeout prematurely.

 * Fixed issue where user-defined pool name would be overridden by the
   automatically generated name.

 * Fixed NPE when one of either username and password is defined, and the
   other is null.

 * Fixed issue tracking the statements when there are mixed statement
   types (Statement, PreparedStatement, etc.) open on the connection and
   the number of unclosed statements exceeds 32.
 
 * Fixed issue where housekeeping threads would add idle connections
   even when minimumIdle was 0.

 * Fixed issue where Wrapper.isWrapperFor() and Wrapper.unwrap() calls
   did not recurse as per specification.

 * HikariDataSource now implements the Closable interface.

 * Integrated change to allow specifying a ThreadGroup for thread
   creation in certain restricted environments.

If you encounter any issues with HikariCP please report them on the github.com issue tracker.