I was trying to run a Clojure project from source using -X on a server that can only access the internet via a HTTP proxy. This is a linux server, with environmental variables and a maven .m2/settings.xml setting the proxy to use correctly. Just in case, I also added the -J-Dhttps.proxyHost and proxyPort settings to my command line. ie : I'm choosing the same proxy settings in 3 different ways: maven settings, -J command line and env variables.

When resolving dependencies on clojars, or using maven install using a pom.xml created on a machine not behind a proxy, dependency resolution worked. However, the Clojure cli tool could not seem to pull down dependencies itself, getting a timeout.

The only fix was for me to build a pom.xml on another machine on another network:

$ clj -X deps mvn-pom

And then copy that file to the protected machine, and run:

$ mvn dependency:resolve

$ mvn install

Further invocations of clj then would use the local .m2 cache and work fine.

It therefore appears that in some way, tools.deps isn't using the proxy settings set either from the maven configuration or from the java command line (or from the environmental variables, but not sure any JVM project does that anyway).

I was hoping to be able to provide a minimal reproducible example, but haven't been able to do so outside of the live environment.

TLDR: if you are stuck behind a proxy and cannot download dependencies, try generating a pom.xml and using maven instead. TLDR: there may be a bug in tools.deps that means that at least one of the network calls does not use the proxy settings, such that the call fails with a timeout. I can't prove this however.

It should be using the maven settings.xml proxy settings

Can you tell if it depends which maven repo (central vs clojars)?

The -J won’t do anything - that affects your program jvm, not the jvm that downloads deps. You can set those settings in CLJ_JVM_OPTS env var if you want to try that

Yes I think you are right in that it worked for some dependencies, but not all, but I'd have to be back in the office to double check which way around it was. I also specify another third-party repo in my deps.edn so it might be one or more of the three. All downloaded when using maven directly. I can try again and see if I can get a more verbose debug output when I'm back in office. Didn't know about the CLj_JVM_OPTS option but will try that as well.

The proxy doesn’t enforce any authentication?

Yes it does. But I get a timeout not an auth failure and the key thing is that maven works so I have my .m2 config correct. I do recall it logging downloads from at least one repository but I’ll do more sleuthing as I can’t recall off hand which appeared to ‘block’.

maybe it's just taking too long via the proxy?

I will do a bit more investigative work and check it isn't stalling with a specific repo but that still wouldn't explain the fact that maven works.

Unless the timeout is configured differently in maven? :thinking_face:

Pretty sure the maven process looked like it was downloading the whole internet (as it usually does) very quickly but I will double check.