In environments where the internet is accessed via a proxy, clj fails to resolve (download) Maven artifacts and instead exits with an opaque error message.
Proxies should be supported out of the box as they are common in corporate environments.
Support for configuring a proxy server could be added in deps.edn, or automatically by inspecting http_proxy, https_proxy etc. environment variables.
Maven settings.xml can also include proxy information, and this is ignored.