- add play-cache-alone
- compile by scala 2.11.11, sbt 0.13.15 (with sbt-coursier plugin)
- add
play.libs.F,play.libs.Scalaclasses toplay-alone - tranfer repository github url from giabao/playframework-standalone to ohze/playframework-standalone
- merge with play 2.5.3
- play-alone now depends on play-iteratees 2.6.0
- to keep play-alone minimal, in previous versions,
we put classes that only play-ws-alone depends on directly in play-ws-alone.
In v2.5.3, we put those classes into a new lib
ws-core-deps. - migration: see [Migrate.md]
- merge with play source #baec3da (2.4.x branch at 10 Nov 2015)
- update dependencies
- add play-ws-alone
- update HikariCP 2.3.9 -> 2.4.1
- update play 2.4.2 (require java 8)
- update scala 2.11.7 & not cross compile to scala 2.10.x
- RENAME & split
play-jdbc-standaloneto 2 librariesplay-alone&play-jdbc-alone. You can use the plainplay-jdbclibrary withplay-alone:
libraryDependencies ++= Seq(
"com.sandinh" %% "play-alone" % "2.4.2",
"com.typesafe.play" %% "play-jdbc" % "2.4.2"
exclude("com.typesafe.play", "play_" + scalaBinaryVersion.value)
)
update slf4j-api 1.7.10, scala 2.11.5, play-hikaricp 1.7.2
update play-hikaricp 1.7.1
-
use HikariCP instead of BoneCP (BoneCP author himself has said the library is deprecated, use Hikari),
-
remove AutoCleanConnection. see: playframework/playframework#2445 (comment)
-
add class play.api.Logger (in previous version, this type is just an alias to org.slf4j.Logger). object play.api.Logger is now also an LoggerLike as in the full play version - so, we can use it directly as: Logger.info(..)
-
play-jdbc config now require configs for
user&passwordeven if you use a driver previously do NOT need those configs - ex when use h2 driver. see diff of src/test/resources/conf/application.conf
- review code with play 2.3.2
- update scala 2.11.2
- sync code with play 2.3.0-RC2.
- update scala 2.11.1
- sync code with play 2.3.0-RC1. As a result, play-jdbc-standalone now do NOT depend on scala-io-core
- this version is binary compatible with v2.0.2_2.2.
So, it is compatible with both play 2.2 & play 2.3.
So, I remove
_2.2from version number. - cross compile to scala 2.10 & 2.11
- use sbt-sonatype
Note: _2.2 in version number (from <= v2.0.2_2.2) is the compatible version of (original) Play
-
sync code with play 2.2.2 (I use Beyond Compare to compare & sync playframework/framework/src with play-jdbc-standalone
-
I also update com.typesafe:config from v1.0.2 to 1.2.0 which is binary compatible. @see https://github.com/typesafehub/config/blob/master/NEWS.md
-
NOTE play 2.2.2 use guava 14.0.1 but we already use guava 15.0 in production with both play 2.2.1 & play-jdbc-standalone 2.0.1_2.2 :( with no error be found until now, and play master branch also use 16.0.1 @see http://code.google.com/p/guava-libraries/wiki/ReleaseHistory so we update guava in play-jdbc-standalone. You - as an user of play-jdbc-standalone - can downgrade guava to 14.0.1 as in play 2.2.2
Update bonecp 0.8.0.RELEASE
Version 2 remove dependencies: logback, jul-to-slf4j. This permit us to use play-jdbc-standalone in an existing system that use another logging framework.
Incompatible change in play-jdbc-standalone 2.x:
-
remove object play.utils.Colors
-
type play.api.Logger is just an alias to org.slf4j.Logger
-
The following members in object play.api.Logger is now removed: init, configure, shutdown, ColoredLevel.
If you don't use those members in your code, then ver 2.x is source-compatible with 1.x. (But now, you need manually config your logger)
This version also add som convenient constructors to SimpleApplication
First stable release