Clojure Lein Figwheel报错：Luminus+Reagent项目编译异常

Hey there, looks like you're hitting a dependency download snag when firing up Figwheel for your fresh Luminus + Reagent + SQLite project. This is a pretty common issue, usually linked to corrupted local caches, network connectivity problems, or repository configuration quirks. Let's work through the fixes:

• Clean up your local dependency cache
  Sometimes partial or corrupted dependency files in Leiningen's cache cause this. First run:

  lein clean
  

  Then navigate to your local Maven repository (usually ~/.m2/repository on macOS/Linux, C:\Users\<YourName>\.m2\repository on Windows) and delete the folders for the problematic dependencies: clj-time, joda-time, and conman. If you don't mind re-downloading all your dependencies, you can even delete the entire repository folder to start fresh.

• Verify your repository configuration
  Slow or unreachable Maven/Clojars repositories can block dependency downloads. Check (or create) the ~/.lein/profiles.clj file and make sure it points to reliable repositories. For most users, this setup works:

  {:user {:repositories [["central" "https://repo1.maven.org/maven2/"]
                          ["clojars" "https://repo.clojars.org/"]]}}
  

  If you're in a region where these repos are slow, swap in a mirror like Alibaba's for faster downloads:

  {:user {:repositories [["central" "https://maven.aliyun.com/repository/public"]
                          ["clojars" "https://maven.aliyun.com/repository/clojars"]]}}
  

• Manually download dependencies first
  Instead of jumping straight to Figwheel, let Leiningen handle dependency downloads separately to catch issues early. Run:

  lein deps
  

  Wait for this to complete successfully (no error messages) before running lein figwheel again.

• Check your network connection
  Make sure you can access the repository URLs directly. Try opening the problematic pom URLs (like https://repo.clojars.org/conman/conman/0.7.8/conman-0.7.8.pom) in your browser—if it won't load, you might need to switch networks, disable a VPN that's blocking access, or configure a proxy in Leiningen.

• Update Leiningen to the latest version
  Older versions of Leiningen can have bugs related to dependency resolution. Update it with:

  lein upgrade
  

  If you installed Leiningen via a package manager (like Homebrew on macOS, or apt on Ubuntu), use that tool to update instead (e.g., brew upgrade leiningen).

Once you've tried these steps, fire up lein figwheel again—it should pull down the necessary dependencies without hitting those errors.

内容的提问来源于stack exchange，提问作者Vasco Ferreira