Clojurians Log v2

If the namespace is being added automatically when a new file is created in cider, then it's clj-refactor at work. The namespace is not added if clj-refactor is not enabled. So take a look at that project for options. Also try the clojure-mode refactoring to manually add the namespace, see if that respects the path set in the deps.edn file

Hey all, another question (and I'm not even sure it's a cider question specifically): is there a way to suppress warnings? I'm doing something vaguely hacky and don't want to see my repl light up with red warnings all the time

Evaluate code in source code buffers is way more efficient way of coding (hacking). With that approach you don't need to have the REPL buffer shown...

Hi all, @bozhidar will be presenting the Dark CIDER to the London Clojurians Meetup. We will learn all the dark secrects of CIDER directly from its author. RSVP: https://www.meetup.com/London-Clojurians/events/274159509/

So, I'm trying to deal with a boot project and use cider-jack-in-clojurescript. Sadly, this ends in an error. I have tracked down the issue, to classpath conflicts on clojure/clojurescript versions in cider/piggieback 0.5.x. In cider/piggieback 0.4.2 there is no direct dependency on a clojure version. Using that version things work fine. I am curious why the explicit reference to clojure 1.8? This project is using clojure 1.10.

nothing of note seems to have changed. i'm surprised

i also can't determine where the specific dep comes from

clj -Sdeps '{:deps {cider/piggieback {:mvn/version "0.4.2"}}}' -Stree
org.clojure/clojure 1.10.1
  org.clojure/spec.alpha 0.2.176
  org.clojure/core.specs.alpha 0.2.44
cider/piggieback 0.4.2

You can see on clojars that 1.8 is listed as a dependency https://clojars.org/cider/piggieback/versions/0.5.1

and with

(defproject foo "0.0.1"
  :dependencies [[cider/piggieback "0.4.2"]])
....
/t/piggie ❯❯❯ lein deps :tree
OpenJDK 64-Bit Server VM warning: Options -Xverify:none and -noverify were deprecated in JDK 13 and will likely be removed in a future release.
 [cider/piggieback "0.4.2"]
 [clojure-complete "0.2.5" :exclusions [[org.clojure/clojure]]]
 [nrepl "0.7.0" :exclusions [[org.clojure/clojure]]]
/t/piggie ❯❯❯

ah, i was checking with 0.4.2 like an idiot 😞

lein deps :tree
OpenJDK 64-Bit Server VM warning: Options -Xverify:none and -noverify were deprecated in JDK 13 and will likely be removed in a future release.
 [cider/piggieback "0.5.1"]
   [javax.xml.bind/jaxb-api "2.3.1"]
     [javax.activation/javax.activation-api "1.2.0"]
   [org.clojure/clojure "1.8.0"]
   [org.clojure/clojurescript "1.8.51"]
     [com.google.javascript/closure-compiler "v20160315"]
       [args4j "2.0.26"]
       [com.google.code.findbugs/jsr305 "1.3.9"]
       [com.google.code.gson/gson "2.2.4"]
       [com.google.guava/guava "19.0"]
       [com.google.javascript/closure-compiler-externs "v20160315"]
       [com.google.protobuf/protobuf-java "2.5.0"]
     [org.clojure/data.json "0.2.6"]
     [org.clojure/google-closure-library "0.0-20151016-61277aea"]
       [org.clojure/google-closure-library-third-party "0.0-20151016-61277aea"]
     [org.clojure/tools.reader "1.0.0-beta1"]
     [org.mozilla/rhino "1.7R5"]
 [clojure-complete "0.2.5" :exclusions [[org.clojure/clojure]]]
 [nrepl "0.7.0" :exclusions [[org.clojure/clojure]]]

this seems fatal

the fact that it has clojure, clojurescript and closure-compiler around seems pretty fatal

https://github.com/nrepl/piggieback/issues/118

Thank you so much @dpsutton

no problem. sorry about that. hopefully @bozhidar can create a clean jar soon. i'm a bit surprised the version profile is put in there

if i do lein jar and then

clj -Sdeps '{:deps {cider/piggieback {:local/root "target/piggieback-0.5.1.jar"}}}' -Stree
org.clojure/clojure 1.10.1
  org.clojure/spec.alpha 0.2.176
  org.clojure/core.specs.alpha 0.2.44
cider/piggieback /Users/dan/projects/dev/piggieback/target/piggieback-0.5.1.jar

so perhaps if you clone it, lein jar && lein install it will work for you? then you could confirm that all is well

That does indeed fix the issue for me locally

can you add that to the issue then @jimmy? with this stuff its nice that there's some confirmation that the new jar has a good chance of being correct

Posted

Piggieback 0.5.2 is out with fixed dependencies. Thanks for spotting and reporting this!

thanks for the release @bozhidar!