Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update dependencies #47

Merged
merged 4 commits into from Dec 30, 2020
Merged

Update dependencies #47

merged 4 commits into from Dec 30, 2020

Conversation

dotemacs
Copy link
Contributor

I updated it because I came across an issue where I had

org.clojure/tools.deps.alpha {:mvn/version "0.9.857"}

declared in a project's deps.edn.

I used the setup as per the README in my ~/.clojure/deps.edn:

:aliases {:outdated {:extra-deps {olical/depot {:mvn/version "2.0.1"}}
          :main-opts ["-m" "depot.outdated.main"]}}

and I got an error:

Syntax error (FileNotFoundException) compiling at (depot/outdated/update.clj:1:1).
Could not locate clojure/tools/deps/alpha/reader__init.class, clojure/tools/deps/alpha/reader.clj 
or clojure/tools/deps/alpha/reader.cljc on classpath.

Then collected the info about it and was about to create a new issue
when I saw this issue about API change in tools.deps.alpha:
#46 and kind of "got distracted" and upgraded the dependencies,
creating this PR.

But really, all I had to do was change the above alias to:

:aliases {:outdated {:replace-deps {olical/depot {:mvn/version "2.0.1"}}
                     :main-opts ["-m" "depot.outdated.main"]}}

NOTE: :replace-deps instead of :extra-deps.

Then I updated more dependencies and fully qualified existing artifacts to suppress warnings.

I updated it because I came across an issue where I had

org.clojure/tools.deps.alpha {:mvn/version "0.9.857"}

declared in a project's deps.edn.

I used the setup as per the README in my ~/.clojure/deps.edn:

:aliases {:outdated {:extra-deps {olical/depot {:mvn/version "2.0.1"}}
                     :main-opts ["-m" "depot.outdated.main"]}}

and I got an error:

Syntax error (FileNotFoundException) compiling at (depot/outdated/update.clj:1:1).
Could not locate clojure/tools/deps/alpha/reader__init.class,
clojure/tools/deps/alpha/reader.clj or
clojure/tools/deps/alpha/reader.cljc on classpath.

Then collected the info about it and was about to create a new issue
when I saw this issue about API change in tools.deps.alpha:
Olical#46 and kind of "got distracted"
and upgraded the dependencies, creating this PR.

But really, all I had to do was change the above alias to:

:aliases {:outdated {:replace-deps {olical/depot {:mvn/version "2.0.1"}}
                     :main-opts ["-m" "depot.outdated.main"]}}

NOTE: :replace-deps instead of :extra-deps.
Seeing as I'm updating the dependencies, updating it to the latest
stable release of CIDER
This is to prevent the warnings:

DEPRECATED: Libs must be qualified...
The example I added works, without any code change, but if the
previous example is used:

$ clojure -Sdeps '{:deps {olical/depot {:mvn/version "2.0.1"}}}' -m depot.outdated.main
Syntax error (FileNotFoundException) compiling at (depot/outdated/update.clj:1:1).
Could not locate clojure/tools/deps/alpha/reader__init.class,
clojure/tools/deps/alpha/reader.clj or clojure/tools/deps/alpha/reader.cljc on classpath.

This is how deps.edn looks:

$ cat deps.edn
{:paths ["src"]
 :deps {org.slf4j/slf4j-simple {:mvn/version "1.7.29"}
        org.clojure/tools.deps.alpha {:mvn/version "0.9.857"}}
 :mvn/repos {"central" {:url "https://repo1.maven.org/maven2/"}
             "clojars" {:url "https://repo.clojars.org/"}}}
@Olical
Copy link
Owner

Olical commented Dec 30, 2020

Oh this is great! Thanks! I didn't see that tools.deps changed the API, I'm guessing it's more than just a name change, I'll take a look.

@Olical Olical merged commit f9ca4cb into Olical:master Dec 30, 2020
@dotemacs dotemacs deleted the update-dependencies branch December 30, 2020 12:16
@Olical
Copy link
Owner

Olical commented Dec 30, 2020

Repo yak shaving complete, version published to clojars! v2.1.0

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants