Skip to content

Commit

Permalink
Releases version 2.1.0
Browse files Browse the repository at this point in the history
  • Loading branch information
marcospereira committed Dec 27, 2015
1 parent 4b819f8 commit 2617ebc
Show file tree
Hide file tree
Showing 3 changed files with 9 additions and 2 deletions.
6 changes: 6 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,11 @@
# Changelog

## Version 2.1.0 - 2015/12/27

1. PR-71 - Upgrade Playframework to version 2.3.10
2. GH-70 - Fix problem related to use logSql with JNDI
3. Upgrade HikariCP to version 2.4.3

## Version 2.0.6 - 2015/05/31

1. Upgrade Playframework to version 2.3.9
Expand Down
3 changes: 2 additions & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -24,6 +24,7 @@ Here is how HikariCP is working for us:

| Version | HikariCP | Play | Docs reference |
|--------:|---------:|------:|:---------------------------------|
| 2.1.0 | 2.4.3 | 2.3.10 | [Release 2.1.0](https://github.com/edulify/play-hikaricp.edulify.com/blob/2.1.0/README.md)|
| 2.0.6 | 2.3.8 | 2.3.9 | [Release 2.0.6](https://github.com/edulify/play-hikaricp.edulify.com/blob/2.0.6/README.md)|
| 2.0.5 | 2.3.7 | 2.3.8 | [Release 2.0.5](https://github.com/edulify/play-hikaricp.edulify.com/blob/2.0.5/README.md)|
| 2.0.4 | 2.3.6 | 2.3.8 | [Release 2.0.4](https://github.com/edulify/play-hikaricp.edulify.com/blob/2.0.4/README.md)|
Expand Down Expand Up @@ -60,7 +61,7 @@ There are just a few steps to properly configure the plugin:

Add the following dependency to your `project/build.sbt` or `project/Build.scala`:

"com.edulify" %% "play-hikaricp" % "2.0.6"
"com.edulify" %% "play-hikaricp" % "2.1.0"

### Step 2: Disable default `dbplugin`

Expand Down
2 changes: 1 addition & 1 deletion build.sbt
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
name := "play-hikaricp"

version := "2.0.6"
version := "2.1.0"

scalaVersion := "2.11.7"

Expand Down

0 comments on commit 2617ebc

Please sign in to comment.