[2.3.8] [warn] what are evicted libraries?

[Andy Czerwonka]

I updated to 2.3.8 and I see a couple of warnings.

I get this when I run the activator.

[warn] There may be incompatibilities among your library dependencies.

[warn] Here are some of the libraries that were evicted:

[warn] * com.typesafe.sbteclipse:sbteclipse-plugin:2.3.0 -> 3.0.0

[warn] Run 'evicted' to see detailed eviction warnings

and this when I run evicted as per the instructions.

[warn] There may be incompatibilities among your library dependencies.

[warn] Here are some of the libraries that were evicted:

[warn] * io.netty:netty:3.6.3.Final -> 3.9.3.Final (caller: com.typesafe.play:play_2.11:2.3.8, com.typesafe.netty:netty-http-pipelining:1.1.2)

Not sure what to do about it. I can't find any docs around this.

-andy

[Daniel Manchester]

Hi,

If I recall correctly, sbt (which underpins activator) uses Apache Ivy to manage dependencies. If two different modules of a project declare the same dependency, but the declarations reference different versions of that dependency, Ivy will generally "evict" the lower-numbered version and only keep the higher-numbered one. (More info here.)

In the first warning, the dependency in question is "sbteclipse-plugin". The dependency declaration referencing version 3.0.0 is probably the one in ivy.xml here:

http://repo.typesafe.com/typesafe/simple/ivy-releases/com.typesafe.play/sbt-plugin/scala_2.10/sbt_0.13/2.3.8/ivys/

Maybe you're getting an old, pre-Play 2.3.8 version of "sbt-plugin" in the mix that has a version 2.3.0 declaration?

Dan

[Andy Czerwonka]

I think I solved it. There was an eclipse shim file that was created when I created the project and it expressly declared 2.3.0. I removed it and the warning is gone.

[Ajay Kumar]

I am also getting this warning. Where did you find the eclipse shim file?