Dependency resolution error

[Noah-Kennedy]

I was attempting to import this project using Leinengen when this happened:

5/5/2018
12:15 PM Dependency resolution error
Error synchronising rmc-core-2018-2019:0.1.0-SNAPSHOT:
Failed to collect dependencies at clj-serial:clj-serial:jar:2.0.4-SNAPSHOT -> com.sparetimelabs:purejavacomm:jar:1.0.0

My project.clj is here:

(defproject rmc-core-2018-2019 "0.1.0-SNAPSHOT"
  :description "FIXME: write description"
  :url "http://example.com/FIXME"
  :license {:name "Eclipse Public License"
            :url "http://www.eclipse.org/legal/epl-v10.html"}
  :dependencies [[org.clojure/clojure "1.8.0"]
                 [venantius/pyro "0.1.2"]
                 [aleph "0.4.4"]
                 [clj-serial "2.0.4-SNAPSHOT"]]
  :main ^:skip-aot rmc-core-2018-2019.core
  :target-path "target/%s"
  :profiles {:uberjar {:aot :all}
             :dev {:dependencies [[jonase/eastwood "0.2.5" :exclusions [org.clojure/clojure]]]}})

Does anyone know what causes this problem or how to solve it?

Edit 1:
Seems like an issue with PureJavaComms not using TLS.

Edit 2:
Fixed the issue by adding this to the end of my project.clj file:

(require 'cemerick.pomegranate.aether)
(cemerick.pomegranate.aether/register-wagon-factory!
  "http" #(org.apache.maven.wagon.providers.http.HttpWagon.))

I guess it was lack of https on PureJavaComms. Not sure if their is a fork that uses https out there. If not, someone could make one and add it to maven. We could then change the dependency in this project. That may not be worth the effort, so it may be better to just add something to README.md about this. I can make a commit to a new branch with the readme change added, if everyone is alright with that. We can merge it in later.

Edit 3:
I noticed that someone already added an issue to the offending repository here. Let's hope this get's addressed soon.

[WhittlesJr]

I believe all is well as of clj-serial 2.0.5

[Noah-Kennedy]

I'll take a look at this tomorrow. I'll close this issue if it's solved.

[WickedShell]

@Noah-Kennedy this should have been fixed with 2.0.5 can you confirm that it's fine?