Play WS 1.1.8 and Play Ebean 4.1.3

marcospereira · 2018-05-02 21:27:01 UTC

Hi Play Community,

We had just released Play WS 1.1.8 and Play Ebean 4.1.3.

Play WS 1.1.8 is a patch release that has a performance optimization made by @pettyjamesm (thank you!).

Play Ebean 4.1.3 brings new version os Ebean and Ebean Agent. We jumped from 4.1.0 to 4.1.3 because of some network problems when releasing 4.1.1 and 4.1.2, so they were considered failed releases.

Best.

KoenDG · 2018-05-08 15:16:08 UTC

Is it possible to use library version higher than used by the Play project itself?

For instance, Play 2.6.13 uses playWS 1.1.7

github.com

playframework/playframework/blob/2.6.13/framework/project/Dependencies.scala#L268


)


// Must use a version of ehcache that supports jcache 1.0.0
val ehcacheVersion = "2.10.4"
val playEhcacheDeps = Seq(
  "net.sf.ehcache" % "ehcache" % ehcacheVersion,
  "org.ehcache" % "jcache" % "1.0.1"
) ++ jcacheApi


val caffeineVersion = "2.5.6"
val playWsStandaloneVersion = "1.1.7"
val playWsDeps = Seq(
  "com.typesafe.play" %% "play-ws-standalone" % playWsStandaloneVersion,
  "com.typesafe.play" %% "play-ws-standalone-xml" % playWsStandaloneVersion,
  "com.typesafe.play" %% "play-ws-standalone-json" % playWsStandaloneVersion
) ++
  (specsBuild :+ specsMatcherExtra).map(_ % Test) :+
  mockitoAll % Test


val playAhcWsDeps = Seq(
  "com.typesafe.play" %% "play-ahc-ws-standalone" % playWsStandaloneVersion,

Does my defining of version 1.1.8 in a project that uses Play 2.6.13 “override” all internal uses also during build?

marcospereira · 2018-05-12 14:29:28 UTC

Yes, if you add 1.1.8 to your build, that version should be used and 1.1.7 will be evicted.