Multiple dependencies with the same organization/name ...

[Sam Halliday]

Hi all,

Since upgrading to sbt 0.13.8 I get a *lot* of errors of this nature (i.e. same thing repeated over and over):

[warn] Multiple dependencies with the same organization/name but different versions. To avoid conflict, pick one version:

[warn]  * org.scala-lang:scala-library:(2.11.6, 2.11.4)

[warn]  * org.scala-lang.modules:scala-parser-combinators_2.11:(1.0.1, 1.0.2, 1.0.3)

[warn]  * org.scala-lang.modules:scala-xml_2.11:(1.0.1, 1.0.3)

I'm actually depending on explicit versions of all these libraries so I believe this is a bug in the warning code.

To reproduce, grab

  https://github.com/ensime/ensime-server/blob/master/project/EnsimeBuild.scala

upgrade to 0.13.8, uncomment the commented cache lines (we were waiting for 0.13.7 bugs to be fixed), and typo `sbt gen-ensime`.

Best regards,

Sam

[Stevo Slavić]

I had/have same problem, and reported it some time ago, no reply. Repeating it again:

With just sbt version bumped, I noticed in IntelliJ new warnings:

2:04:09 PM SBT project import

           [warn] Multiple dependencies with the same organization/name but different versions. To avoid conflict, pick one version:

           [warn]  * org.scala-lang:scala-compiler:(2.10.3, 2.10.5)
           [warn]  * org.scala-lang:scala-reflect:(2.10.4, 2.10.5)
           [warn]  * junit:junit:(4.10, 4.11)
           [warn]  * org.hamcrest:hamcrest-core:(1.1, 1.3)

I have no direct junit dependency declared, nor hamcrest-core. They are transitive dependencies of various testkit libs. By docs ( http://www.scala-sbt.org/0.13/docs/Library-Management.html ) "The default conflict manager chooses the latest revision..". I guess now it also reports a warning, so this is a feature ( https://github.com/sbt/sbt/pull/1634 ), and to eliminate warning one is expected to pick a single version through dependencyOverrides. Correct?

Kind regards,

Stevo Slavic.

--
You received this message because you are subscribed to the Google Groups "sbt-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sbt-dev+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/sbt-dev/793d90b4-5da0-418b-8f77-ded7b37ebce5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[eugene yokota]

I'm guess this is actually a bug introduced by #1899, which is intended to reduce warning.

Could you report this?

-eugene

  [1899]: https://github.com/sbt/sbt/pull/1899

--

[Dale Wijnand]

The error looks to be from another code path (still the ivy module clearly) but I'd be happy to follow up on this.

Dale

To view this discussion on the web visit https://groups.google.com/d/msgid/sbt-dev/CA%2BCq6KRuSykC5ALWL1WoNjfaGD3yF_Vw2Zhzv-70rXSaAZwu9w%40mail.gmail.com.

[Sam Halliday]

Ok, I'll assume Dale will raise the ticket. Please give me a mention so that I receive notifications.

You received this message because you are subscribed to a topic in the Google Groups "sbt-dev" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/sbt-dev/61J8cnQrsxU/unsubscribe.
To unsubscribe from this group and all its topics, send an email to sbt-dev+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/sbt-dev/CAG9PQvXzjTOsiV%2BRi8Hw4RY3q66b_XgK_3x0exLoxfq07bHvtA%40mail.gmail.com.

[Dale Wijnand]

I meant more that I'd look into the ticket, but anyways now I have the ensime-server sources locally :)

https://github.com/sbt/sbt/issues/1933

Dale

To view this discussion on the web visit https://groups.google.com/d/msgid/sbt-dev/CALR_T9AzNV2xORfSaM3ExhBd9txJ1Oh-q9ENh1Jqm4yxgiLZKQ%40mail.gmail.com.