Solve Play 2.5 version conflicts
See original GitHub issueVersion 2.0.0 supports both Play 2.4 and Play 2.5 but in plugins.sbt Play 2.4 is used. That couse version conflicts during sbt’s dependency resolving:
[warn] * com.typesafe.play:play_2.11:2.5.18 is selected over 2.4.0
[warn] +- com.typesafe.play:play-cache_2.11:2.5.18 (depends on 2.5.18)
[warn] +- com.typesafe.play:play-jdbc-api_2.11:2.5.18 (depends on 2.5.18)
[warn] +- com.typesafe.play:play-logback_2.11:2.5.18 (depends on 2.5.18)
[warn] +- com.typesafe.play:play-ws_2.11:2.5.18 (depends on 2.5.18)
[warn] +- com.typesafe.play:play-server_2.11:2.5.18 (depends on 2.5.18)
[warn] +- org.julienrf:play-jsmessages_2.11:2.0.0 (depends on 2.4.0)
Issue Analytics
- State:
- Created 6 years ago
- Comments:11 (11 by maintainers)
Top Results From Across the Web
Conflict between Play! Framework 2.5 and gRPC 0.13
There are conflicts with Play 2.5.0 because Netty 4 and Netty 4.1 have both the same dependencies artifactId (then 4.1 version evicts ...
Read more >Dependency conflicts · Issue #8429 · playframework ... - GitHub
There are several dependency conflicts while compiling Play 2.6.13 application Play Version (2.5.x / etc) 2.16.13 API (Scala / Java ...
Read more >Play Change Log
Play 2.5.14 “Streamy”. Released 6 Apr 2017. 7200: Upgrade akka and akka-http; 7182: Upgrade logback dependency to fix 5 secs delays in unittests ......
Read more >Will Play 2.5.x upgrade to netty 4.1? - Google Groups
I was going to migrate to Play 2.5.x when it is released but I had to stick with Play 2.4 due to a...
Read more >migrate a playframework app from 2.3 to 2.5 - Blog
Migration from 2.3 to 2.4 · 1. Update the sbt config to play 2.4 · 2. Fix compilation errors · 3. Run the...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
You should target the
2.1.x
branch.Thanks, and I just added it to my project, everything is okay now, the conflicts are gone.