CODEWITHSUNDEEP
playframeworkplayframework-2.3deadbolt
Programmer
Programmer

Reputation: 325

Incompatibilities among your library dependencies after up-gradation from play 2.4 version to play 2.5.0

I have recently upgraded my project from play framework 2.4.0 to 2.5.0 and when I build it I am getting so many library incompatibilities issue which I am unsure about how to resolve it. Can anyone has any idea how can we resolve such issues.

I am just sharing the sample as list is quite big:

[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 have noticed that all above warns are coming because I am using deadbolt2 library version as: 

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

If I remove above dependency then all warns go away. There is not other latest version available for deadbolt2. Not sure what I should do now. Please suggest.

Upvotes: 4

Views: 1549

Answers (2)

Programmer
Programmer

Reputation: 325

Thanks everyone for looking at this questions and trying to help me in this. It's was actually the deadbolt 2 dependency that I was using with Playframework 2.5.0.

I was using:

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

Now am using below, which has actually solved the issue:

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

Upvotes: 0

Steve Chaloner
Steve Chaloner

Reputation: 8202

Versioning in Deadbolt follows the same x.y version of Play, so Deadbolt 2.4 is for Play 2.4, Deadbolt 2.5 is for Play 2.5 and so on.

Deadbolt 2.5.0 was released today, so if you update your version to "be.objectify" %% "deadbolt-scala" % "2.5.0" you should be fine.

This is documented here.

Upvotes: 1

Related Questions