This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # beginners (22)
- # boot (652)
- # boulder-clojurians (1)
- # cider (19)
- # cljs-dev (3)
- # clojure (158)
- # clojure-dev (8)
- # clojure-nl (1)
- # clojure-poland (5)
- # clojure-russia (27)
- # clojure-sg (3)
- # clojure-za (4)
- # clojurescript (44)
- # community-development (2)
- # core-async (17)
- # core-logic (10)
- # css (1)
- # cursive (35)
- # data-science (5)
- # datascript (1)
- # datomic (90)
- # editors-rus (3)
- # events (3)
- # hoplon (90)
- # ldnclj (19)
- # lein-figwheel (2)
- # leiningen (1)
- # om (225)
- # reagent (1)
- # uncomplicate (27)
@micah: So the problem is that the plugin is messing with :eval-in - I’ll see if I can find a fix for that.
@cfleming: with 0.1.67 a dependency like yada:1.0.0-20150903.093751-9 is not being picked up
is this related to https://github.com/cursiveclojure/cursive/issues/1113?
If you change it to yada:1.0.0-SNAPSHOT, I believe it should work. Is there a reason you’re depending on an explicit version of a snapshot?
@stijn: Interesting use case though, I can imagine that you might want to pin to a specific snapshot version.
I’m not entirely sure how I’ll fix that one, since it’s tricky to support both -SNAPSHOT versions and the explicit ones.
@cfleming: With the -a flag (auto run), speclj will stay alive re-run any specs affected by file changes. What’s the fix? Is it in the script you pasted?
@cfleming: Also, as I try to debug this, I get a Cursive error every time I “lein install” speclj: java.io.EOFException: Unexpected end of ZLIB input stream, compiling:(leiningen/spec.clj:49:7) I have to restart InstalliJ to get passed this.
Ah, I was running into this issue with snapshot dependencies the other day too, but I thought I was doing something wrong
It’s fairly common for us to pin a snapshot dep, especially in the CLJS world where things move so quickly
@danielcompton: Yeah, that makes sense. I’ll see if I can do something sensible with that case.
@micah: Ah, that makes sense. The fix is a code fix, I’ll send you a dev build to play with shortly. Are you on IntelliJ 14.1?
@danielcompton: The problem is when you have a snapshot dep brought from a repository. The deps come back with two versions, the “resolved version”, which is the
-20150903.093751-9 one, or the “base version” which is the
project.clj will only have one of those two versions specified, and it looks like I really have to try to match both to the dependencies which come back.
It gets tricky when you have snapshot deps which depend on other snapshots, especially if some are pinned and some are not.
So that case was the case I fixed on the weekend, because when you depend on
-SNAPSHOT, aether (lower-case, the Clojure one) returns the resolved version, and Cursive didn’t match them correctly.