Fork me on GitHub
#cider
<
2016-12-07
>
nonrecursive14:12:35

hey yall, has anyone else gotten this message when trying to use cider-jack-in with boot?

Starting nREPL server via /usr/local/bin/boot -d org.clojure/tools.nrepl\:0.2.12 -d refactor-nrepl\:2.3.0-SNAPSHOT -d cider/cider-nrepl\:0.14.0 repl -m refactor-nrepl.middleware/wrap-refactor -m cider.nrepl/cider-middleware -s wait...
error in process sentinel: nrepl-server-sentinel: Could not start nREPL server: Exception in thread "main" java.lang.reflect.InvocationTargetException
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at Boot.main(Boot.java:258)
Caused by: java.lang.IllegalArgumentException: Bad artifact coordinates org.clojure:clojure:jar:, expected format is <groupId>:<artifactId>[:<extension>[:<classifier>]]:<version>

dpsutton14:12:44

and it works correctly with lein?

dpsutton14:12:30

like the jars in your ~/.m2 directory aren't bad?

nonrecursive14:12:35

works ok with lein

nonrecursive14:12:50

i tried running /usr/local/bin/boot -d org.clojure/tools.nrepl\:0.2.12 -d refactor-nrepl\:2.3.0-SNAPSHOT -d cider/cider-nrepl\:0.14.0 repl -m refactor-nrepl.middleware/wrap-refactor -m cider.nrepl/cider-middleware -s fromt he command line and that works fine too

dpsutton14:12:54

can you crank up a lein repl in the same directory?

dpsutton14:12:16

sorry, not a lein repl, but exactly what you did

dpsutton14:12:22

that's the verbatim string that CIDER does?

dpsutton14:12:56

she had the wrong version of clojure specified in her project or boot file

dpsutton14:12:39

also, from your message, Bad artifact coordinates org.clojure:clojure:jar:, that looks a little malformed

dpsutton14:12:46

is it missing a version?

dpsutton14:12:55

the colon then comma makes me think some config is off

nonrecursive14:12:24

hmmm yeah, I just can’t figure out where that might be coming from

dpsutton14:12:50

is it possible to post your build.boot file here if its not too sensitive?

dpsutton14:12:13

also, do you have any profile files lying around? ~/.boot or whatever boots config file is?

nonrecursive14:12:38

(set-env!
  :source-paths   #{"src"}
  :resource-paths #{}
  :target-path    "target/build"
  :dependencies   '[[org.clojure/clojure         "1.9.0-alpha14" :scope "provided"]
                    [boot/core                   "2.5.5"         :scope "provided"]
                    [adzerk/boot-test            "1.1.1"         :scope "test"]
                    [adzerk/bootlaces            "0.1.13"        :scope "test"]
                    [org.clojure/test.check      "0.9.0"         :scope "test"]
                    [org.clojure/tools.namespace "0.2.11"        :scope "test"]
                    [aysylu/loom "0.6.0"]
                    [medley "0.8.3"]])

(require '[adzerk.bootlaces :refer :all]
         '[adzerk.boot-test :refer :all])


(def +version+ "0.1.0")
(bootlaces! +version+)

dpsutton14:12:41

also, is this a project that has been working and recently stopped? is it a new project from a template or cloned from someone?

nonrecursive14:12:02

it hasn’t worked, and it seems I can’t boot jack in with other projects where I was able to previously

dpsutton14:12:01

so we definitely have a regression

dpsutton14:12:14

do you use spec in this project?

dpsutton14:12:40

wondering if dropping down to 1.8.0 fixes this

nonrecursive14:12:48

it might be something I changed in one of my .boot files

dpsutton14:12:13

and 1.9.0-alpha14 definitely exists

nonrecursive14:12:25

it’s looking like it has to do with the boot.properties file

dpsutton14:12:14

that's a global boot file?

dpsutton14:12:18

can you post here?

nonrecursive14:12:58

ok I think I figured it out

nonrecursive14:12:20

my emacs config was set to copy BOOT_CLOJURE_VERSION from the environment, but that wasn’t actually set in my environment, so in the emacs environment I essentially had BOOT_CLOJURE_VERSION=””

nonrecursive14:12:44

that’s why the artifact was coordinates were bad, because the clojure version was missing

nonrecursive14:12:14

thanks for helping me figure it out 🙂 🙂 🙂

dpsutton14:12:19

hmm, maybe CIDER should default to 1.7 (its minimum supported version) if this is the case

dpsutton14:12:35

ha i think i was a rubber duck. but glad it got worked out

nonrecursive14:12:25

it seems like a weird edge case, I wonder if it might be better have some kind of error message. or maybe print a message and default to 1.7

parkeristyping23:12:09

When I use cider-jack-in, eldoc works (i.e. shows me function info in the minibuffer), but when I cider-connect to a repl started with clojure.tools.nrepl.server/start-server, I don’t see anything in the minibuffer

parkeristyping23:12:06

any ideas why? or can anyone point me in the right direction?

parkeristyping23:12:57

oh. passing the handler here as an option worked: https://github.com/clojure-emacs/cider-nrepl

(clojure.tools.nrepl.server/start-server :handler cider.nrepl/cider-nrepl-handler)