Thanks, Gary! Kevin tried a :verbose require, and the last few lines
involved loading tools.reader and the ExceptionInfo class, so it seems very
likely that you are correct about the problem. I have suggested trying this
exclusion, does that look like it might do the trick? (I’m not entirely
confident of the semantics of Leiningen exclusions and how they propagate
to recursive dependencies):
:dependencies [[org.clojure/clojure "1.7.0"]
[org.clojure/tools.reader "0.10.0"] ; Or perhaps 1.0.0-alpha1
[afterglow "0.1.4" :exclusions [org.clojure/tools.reader]]]
On Sunday, November 8, 2015 at 1:17:47 PM UTC-6, Gary Trakhman wrote:
>
> Just a guess, since your project has many dependencies, and I have little
> time right now, but I had a recent issue with tools.reader <=0.9.2 and the
> ExceptionInfo class. The maven artifacts for tools.reader bundled .class
> files, and triggered this bug: http://dev.clojure.org/jira/browse/CLJ-1639
>
> Our stacktraces looked like this:
> Caused by: java.lang.ExceptionInInitializerError
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:348)
> at clojure.lang.RT.classForName(RT.java:2154)
> at clojure.lang.RT.classForName(RT.java:2163)
> at clojure.lang.RT.loadClassForName(RT.java:2182)
> at clojure.lang.RT.load(RT.java:436)
> at clojure.lang.RT.load(RT.java:412)
> at clojure.core$load$fn__7859.invoke(core.clj:5866)
> at clojure.core$load.doInvoke(core.clj:5865)
> at clojure.lang.RestFn.invoke(RestFn.java:408)
> at clojure.core$load_one.invoke(core.clj:5671)
> at clojure.core$load_lib$fn__7808.invoke(core.clj:5711)
> at clojure.core$load_lib.doInvoke(core.clj:5710)
> at clojure.lang.RestFn.applyTo(RestFn.java:142)
> at clojure.core$apply.invoke(core.clj:632)
> ...
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateBean(AbstractAutowireCapableBeanFactory.java:1069)
> ... 32 more
> Caused by: java.lang.RuntimeException: Unable to resolve symbol: init in
> this context, compiling:(clojure/tools/reader/impl/ExceptionInfo.clj:1:1)
> at clojure.lang.Compiler.analyze(Compiler.java:6543)
> at clojure.lang.Compiler.analyze(Compiler.java:6485)
> at clojure.lang.Compiler$InvokeExpr.parse(Compiler.java:3791)
> at clojure.lang.Compiler.analyzeSeq(Compiler.java:6725)
> at clojure.lang.Compiler.analyze(Compiler.java:6524)
> at clojure.lang.Compiler.analyze(Compiler.java:6485)
> at clojure.lang.Compiler$BodyExpr$Parser.parse(Compiler.java:5861)
> ...
>
> I'm not sure what's causing leiningen to omit the full stacktrace, but
> it's possible you can get to it with *e from the repl, since you're doing a
> dynamic require.
>
> In this case, we bumped up to 0.10.0 which no longer had the ExceptionInfo
> class nor AOT issue.
>
> On Sun, Nov 8, 2015 at 2:10 PM James Elliott <brun...@gmail.com
> <javascript:>> wrote:
>
>> This weekend I was thrilled to have two people pick up and start
>> experimenting with Afterglow, the live-coding light show software I’ve been
>> working on this year, and both are new to Clojure as well. Unfortunately
>> one is stuck and I am stumped about how to try to help: He’s been able to
>> use Afterglow when running it from source, but when he tries including it
>> as a library in a new Leiningen project, the attempt to require the
>> examples namespace in the REPL, which is the first step in the walkthrough,
>> fails in an utterly cryptic way:
>>
>>
>> (require 'afterglow.examples)
>>
>> CompilerException java.lang.ExceptionInInitializerError,
>> compiling:(afterglow/examples.clj:1:1
>>
>> There is no stack trace shown, nor a root cause, and this leaves me
>> baffled as to how to diagnose it. Starting a new project on my own system
>> works fine. Is there a way we can try to load things in smaller pieces and
>> see the underlying issues?
>>
>> I have suggested trying adding the :verbose flag in the require, and we
>> will see if that helps any, but I am hoping for some other angles of attack
>> too. The issue thread where we are working on this is here:
>> https://github.com/brunchboy/afterglow/issues/7
>>
>> Thanks for any help you can offer me in helping fan these flames of
>> interest!
>>
>> --
>> You received this message because you are subscribed to the Google
>> Groups "Clojure" group.
>> To post to this group, send email to clo...@googlegroups.com
>> <javascript:>
>> Note that posts from new members are moderated - please be patient with
>> your first post.
>> To unsubscribe from this group, send email to
>> clojure+u...@googlegroups.com <javascript:>
>> For more options, visit this group at
>> http://groups.google.com/group/clojure?hl=en
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "Clojure" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to clojure+u...@googlegroups.com <javascript:>.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - please be patient with your
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
---
You received this message because you are subscribed to the Google Groups
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
