Reduce verbosity when resolving artifacts

I was just wondering whether we’ve ever considered only outputting the following types of message when we cannot locate an artifact locally:

       [info] Resolving org.scala-sbt#persist;0.13.5 ...

…who would care if this can be resolved quickly? Perhaps we should only output messages like that if the action takes more than, say, 1 second. Taking this approach would vastly reduce the amount of output from sbt.

WDYT?

[jroper]

I am 100% sure that not one of the millions (a quick calculation reveals that this is a conservative estimate) of resolving messages that have flashed before my eyes over the entire time that I have been using sbt have ever helped me in the slightest. If there’s a resolve error, I see the error message, the resolving info message is not helpful. If there’s a problem with my dependencies, I go to the ivy reports which helps me debug them. The resolving messages do not contain enough information to be helpful in this case. I cannot ever remember a time when a resolving message has been useful. Not once.

But I can tell you that the resolving messages have caused so much pain, mostly with CI, particularly with things like travis that if you turn logging off completely, timeout because you’re not logging, or if you leave it on, fail because you logs exceed 10000 lines, 5000 of which are resolving messages.

These messages should be logged at debug, not info.

[ocramz]

@axel22 I found ivyLoggingLevel := UpdateLogging.Quiet in build.sbt to suppress all the [info] Resolving .. messages