Affects Version/s: None
Fix Version/s: Release 1.3
when Java is in a bad mood, exceptions start flying without any accompanying stack traces. This causes the default REPL's error reporting to barf, as it currently assumes that the first stack trace element always exists. You can see this by trying the following snippet at the REPL several times in succession:
When Java is somewhat angry, you will see the appropriate
Eventually Java gets angrier and stops providing stack traces, causing an aget error in clojure.main instead.
|Status||Open [ 1 ]||Closed [ 6 ]|
|Resolution||Completed [ 1 ]|