Fork me on GitHub
Ben Lieberman18:11:43

I think I don't quite understand how this :mvn/repos key is supposed to work. When I start my REPL, it errors out bc it looks in Maven for the dep I want, and not in the repo I specify here:

{:mvn/repos {"nexus" {:url ""
                      :snapshots {:enabled true}}}
 :deps {org.onebusaway/onebusaway-gtfs {:mvn/version "1.3.95-SNAPSHOT"}}}


I forget the exact behavior, but usually when you add a repo like that it is merged into the existing list of repos, doesn't replace the existing list. So it is possible the repo you are giving it isn't exactly correct so it cannot find the artifact there and it is continuing down the list to search in central, etc

Ben Lieberman18:11:55

Yeah, looks like you're right. The versioning for various modules in this repo is really screwy so thanks for finding that out.

Alex Miller (Clojure team)18:11:01

Maven central and clojars are always first and second in the repos checked

Alex Miller (Clojure team)18:11:25

but it shouldn't error out, it should continue to look

Alex Miller (Clojure team)18:11:42

can you drop the actual error here? (or in #C6QH853H8)

Alex Miller (Clojure team)18:11:40

(also you don't need the :snapshots part - the default is to enable a repo for both releases and snapshots)

Alex Miller (Clojure team)18:11:06

one thing you may be hitting is that http is no longer supported by Maven - has to be https (b/c MITM attack)