Skip to content
This repository has been archived by the owner on Apr 25, 2024. It is now read-only.

2.0.0-SNAPSHOT update causes compilation fail #56

Closed
jjpe opened this issue Sep 7, 2013 · 5 comments
Closed

2.0.0-SNAPSHOT update causes compilation fail #56

jjpe opened this issue Sep 7, 2013 · 5 comments

Comments

@jjpe
Copy link

jjpe commented Sep 7, 2013

I've been using 0.2.0-SNAPSHOT for a while now and usually everything works fine (which is excellent).
But I just tried to compile my clojure/android project and lein pulled in lein-droid-0.2.0-20130906.220219-16.pom. SInce then my app refuses to build successfully.

The stacktrace:

Retrieving lein-droid/lein-droid/0.2.0-SNAPSHOT/lein-droid-0.2.0-20130906.220219-16.jar from clojars
Generating R.java...
Compiling 1 source files to /Users/j/Development/clojure/autonomer/target/classes
Compiling Clojure files...
Build type: debug, dynamic compilation: enabled, remote REPL: enabled.
Exception in thread "main" java.lang.RuntimeException: Unable to resolve var: o/*nrepl-port* in this context, compiling:(NO_SOURCE_PATH:1:136)
    at clojure.lang.Compiler.analyzeSeq(Compiler.java:6567)
    at clojure.lang.Compiler.analyze(Compiler.java:6361)
    at clojure.lang.Compiler.analyze(Compiler.java:6322)
    at clojure.lang.Compiler$InvokeExpr.parse(Compiler.java:3624)
    at clojure.lang.Compiler.analyzeSeq(Compiler.java:6562)
    at clojure.lang.Compiler.analyze(Compiler.java:6361)
    at clojure.lang.Compiler.analyze(Compiler.java:6322)
    at clojure.lang.Compiler$InvokeExpr.parse(Compiler.java:3624)
    at clojure.lang.Compiler.analyzeSeq(Compiler.java:6562)
    at clojure.lang.Compiler.analyze(Compiler.java:6361)
    at clojure.lang.Compiler.analyze(Compiler.java:6322)
    at clojure.lang.Compiler$BodyExpr$Parser.parse(Compiler.java:5708)
    at clojure.lang.Compiler$LetExpr$Parser.parse(Compiler.java:6009)
    at clojure.lang.Compiler.analyzeSeq(Compiler.java:6560)
    at clojure.lang.Compiler.analyze(Compiler.java:6361)
    at clojure.lang.Compiler.analyze(Compiler.java:6322)
    at clojure.lang.Compiler$BodyExpr$Parser.parse(Compiler.java:5708)
    at clojure.lang.Compiler$FnMethod.parse(Compiler.java:5139)
    at clojure.lang.Compiler$FnExpr.parse(Compiler.java:3751)
    at clojure.lang.Compiler.analyzeSeq(Compiler.java:6558)
    at clojure.lang.Compiler.analyze(Compiler.java:6361)
    at clojure.lang.Compiler.eval(Compiler.java:6616)
    at clojure.lang.Compiler.eval(Compiler.java:6609)
    at clojure.lang.Compiler.eval(Compiler.java:6582)
    at clojure.core$eval.invoke(core.clj:2852)
    at clojure.main$eval_opt.invoke(main.clj:313)
    at clojure.main$initialize.invoke(main.clj:332)
    at clojure.main$null_opt.invoke(main.clj:367)
    at clojure.main$main.doInvoke(main.clj:445)
    at clojure.lang.RestFn.invoke(RestFn.java:421)
    at clojure.lang.Var.invoke(Var.java:419)
    at clojure.lang.AFn.applyToHelper(AFn.java:163)
    at clojure.lang.Var.applyTo(Var.java:532)
    at clojure.main.main(main.java:37)
Caused by: java.lang.RuntimeException: Unable to resolve var: o/*nrepl-port* in this context
    at clojure.lang.Util.runtimeException(Util.java:219)
    at clojure.lang.Compiler$TheVarExpr$Parser.parse(Compiler.java:650)
    at clojure.lang.Compiler.analyzeSeq(Compiler.java:6560)
    ... 33 more
Compilation failed.

I've since then also tried 0.2.0-beta2 and 0.2.0-beta3.
0.2.0-beta2 works, but 0.2.0-beta3 also refuses to build, and looking at the clojars upload time stamp I'm guessing the issue with beta3 is related to the one in the current 0.2.0-SNAPSHOT.

Any idea what's causing it @alexander-yakushev?

@alexander-yakushev
Copy link
Member

SNAPSHOT version is a pretty unstable right now. This version (and every version since 0.2.0-beta3) requires neko 3.0.0-beta6 to work with). You can use them in combination, or either stick to lein-droid 0.2.0-beta2 until everything settles down).

@jjpe
Copy link
Author

jjpe commented Sep 7, 2013

Ah I see. I guess I'll stick with beta2 for now then.
Any ballpark-figure idea on when things will settle down with the new code base?
I'm asking so that I can plan accordingly for my own app.

@alexander-yakushev
Copy link
Member

They should by the end of this month.

I actually try not to introduce breaking changes anymore, or cover them with some fallback behavior. This one slipped through, although I think I will put some guard on it so it won't fail with older versions of Neko.

@jjpe
Copy link
Author

jjpe commented Sep 7, 2013

I see. I appreciate both the effort and the quick response, so thank you.

@jjpe jjpe closed this as completed Sep 7, 2013
@alexander-yakushev
Copy link
Member

No problem. I shouldn't have really encouraged people to use SNAPSHOT versions, sorry for that.

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

No branches or pull requests

2 participants