From eef3a1ed311f454e064ef81cc287bc604f4cb140 Mon Sep 17 00:00:00 2001 From: Indrajit Raychaudhuri Date: Mon, 12 Mar 2012 05:14:52 +0530 Subject: [PATCH] Adjust mechanism of resolver conflict detection Warn when publish resolver and dependency resolvers have same name but different access mechanism. Multiple resolvers having same name as well as same access mechanism (i.e., equality matching) isn't usually a problem. A common scenario for this would be Maven based resolvers with exact (http based) same access mechanism. Also see #367, #363 --- main/Defaults.scala | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/main/Defaults.scala b/main/Defaults.scala index d07711807..b4c8a24e4 100755 --- a/main/Defaults.scala +++ b/main/Defaults.scala @@ -841,8 +841,9 @@ object Classpaths } ) def warnResolversConflict(ress: Seq[Resolver], log: Logger) { - for ((name, r) <- ress groupBy (_.name) if r.size > 1) { - log.warn("Multiple resolvers configured with the name '" + name + "'. To avoid conflict, Remove duplicate project resolvers (`resolvers`) or rename publishing resolver (`publishTo`).") + val resset = ress.toSet + for ((name, r) <- resset groupBy (_.name) if r.size > 1) { + log.warn("Multiple resolvers having different access mechanism configured with same name '" + name + "'. To avoid conflict, Remove duplicate project resolvers (`resolvers`) or rename publishing resolver (`publishTo`).") } } def pluginProjectID: Initialize[ModuleID] = (sbtVersion in update, sbtBinaryVersion in update, scalaVersion in update, scalaBinaryVersion in update, projectID, sbtPlugin) {