Incompatibility between your library dependencies after improving performance from version 2.4 to play 2.5.0

I recently upgraded my project from play framework 2.4.0 to 2.5.0, and when I create it, I have so many problems with the library that I'm not sure how to resolve it. Can anyone understand how we can solve such problems.

I just use the sample, as the list is quite large:

[warn] There may be incompatibilities among your library dependencies
[warn] Here are some of the libraries that were evicted:
[warn]  * com.typesafe.play:play-netty-server_2.11:2.4.0 -> 2.5.0
[warn]  * com.typesafe.play:play-java_2.11:2.4.0 -> 2.5.0
[warn]  * com.typesafe.play:play-server_2.11:2.4.0 -> 2.5.0

I noticed that all of the above warnings appear because I am using the deadbolt2 library version as:

"be.objectify" % "deadbolt-java_2.11" % "2.4.4"

If I remove the above dependency then all warnings go away. There is no other latest version for deadbolt2. I don’t know what to do now. Please suggest.

+4
2

Deadbolt x.y, Deadbolt 2.4 Play 2.4, Deadbolt 2.5 Play 2.5 ..

Deadbolt 2.5.0 , , "be.objectify" %% "deadbolt-scala" % "2.5.0", .

.

+1

, . deadbolt 2, Playframework 2.5.0.

:

"be.objectify" % "deadbolt-java_2.11" % "2.4.4"

, :

"be.objectify" %% "deadbolt-java" % "2.5.0"
0

All Articles