to minimize the chance of two different Artifact to have the same URL -
these are handled well by the cache if the corresponding URL has not
been downloaded yet, and result in one download locking the file for the
others
...in updateClassifiers.
Also fail if an artifact cannot be fetched in update. A bit risky - might unveil locked errors, that ought to be circumvented.
- Set default verbosity level to 0
- Use the same cache policies as the CLI app everywhere (local-only, then fetch-missing)
- Allow to manually override these via the environment (COURSIER_VERBOSITY and COURSIER_MODE), or Java properties (coursier.verbosity and coursier.mode)
Fixes some publish or publishSigned commands failing, for some
modules having the same dependencies as others (thus previously the same
cache key, so no resolution was done and no Ivy file was generated,
which made the publish or publishSigned command complains).