New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[2.6.5] Eviction warnings appeared after update from 2.6.3 #7832
Comments
Hi @PromanSEW, This is how sbt shows evictions now: These warnings were presented before too, but with a different (and more compact) format. You can change the log level to log only error messages if you want. Just add the following configuration: logLevel := Level.Error We don't plan to manually exclude the transitive dependencies, but you can submit a PR. |
@marcospereira Thanks. evictionWarningOptions in update := EvictionWarningOptions.default
.withWarnTransitiveEvictions(false)
.withWarnDirectEvictions(false) I found this option here: sbt/sbt#1636 (comment) And about excluding: I think Akka dependencies should be fixed at least. |
Eviction warnings for Akka
should be resolved by following Akka's compatibility guideline »Akka HTTP 10.0.x with Akka 2.5.x« as mentioned at akka/akka-http/issues/1452. |
@agebhar1 perhaps I am missing something but inserting the suggested to build.sbt e.g. in the scala starter example seems to make the eviction warning even worse:
|
With sbt 0.13.15 no warnings shown, with sbt 0.13.16 and 1.0.2 getting this:
Using play 2.6.6 no plugins and this is my build:
added the following line in build.sbt removed the warnings:
But I'm getting this
|
@hayd you didn't miss something. I was to optimistic about Akka's compatibility guideline »Akka HTTP 10.0.x with Akka 2.5.x«. The warning from sbt regarding to »akka-actor« and »akka-stream« is okay since
To not disable all eviction warnings you can override a version by
The warning from guava's eviction should be taken seriously since guice depends on 19.0 which is not binary (source) compatible with 22.0 per se. |
@hayd what is the problem with my comment to thumb down? |
@almothafar your post is 1. essentially the same error as first message (and *imo workaround not solution |
@hayd did not take it as offense, I just was wonder why is this 😄 Anyways, I'm looking for solution for this, for now removing warnings helpful for me as a temp solution so DevOps do not get confused :) |
Here are final settings for my project to resolve all eviction warnings. // https://github.com/playframework/playframework/blob/2.6.x/framework/project/Dependencies.scala#L11
val akkaVersion = "2.5.6"
dependencyOverrides ++= Set( // Seq for SBT 1.0.x
"com.typesafe.akka" %% "akka-actor" % akkaVersion,
"com.typesafe.akka" %% "akka-stream" % akkaVersion,
"com.google.guava" % "guava" % "22.0",
"org.slf4j" % "slf4j-api" % "1.7.25"
) Thanks @agebhar1 a lot! |
@PromanSEW @agebhar1 Hi guys. Thank you. Props. ++= Set( would not compile using sbt run BUT maybe because I'm using sbt version 1.0.2 |
@backboardo2 I added a note about |
Thank you both @PromanSEW and @backboardo2 for your feedback 😃 |
## Purpose Lagom already has a whitelist which dependencies are added, so the evictions warnings are just adding noise to the build. ## References 1. playframework/playframework#7832 2. sbt/sbt#1636
## Purpose Lagom already has a whitelist which dependencies are added, so the evictions warnings are just adding noise to the build. ## References 1. playframework/playframework#7832 2. sbt/sbt#1636
## Purpose Lagom already has a whitelist which dependencies are added, so the evictions warnings are just adding noise to the build. ## References 1. playframework/playframework#7832 2. sbt/sbt#1636
Play Version (2.5.x / etc)
2.6.5
Operating System (Ubuntu 15.10 / MacOS 10.10 / Windows 10)
macOS 10.12.6
JDK (Oracle 1.8.0_72, OpenJDK 1.8.x, Azul Zing)
Java(TM) SE Runtime Environment (build 1.8.0_144-b01)
Java HotSpot(TM) 64-Bit Server VM (build 25.144-b01, mixed mode)
Upgrade changes
Behavior after upgrade
I see these warnings in IntelliJ IDEA console every time while loading the project
How to disable these annoyning lines from console output?
Do you have to fix them yourself in Play dependencies?
Temporary fix
#7832 (comment)
The text was updated successfully, but these errors were encountered: