Submitted as
http://code.google.com/p/clojure/issues/detail?id=106
--~--~-~--~~~---~--~~
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
To unsubscribe from th
On Apr 11, 6:13 pm, "John D. Hume" wrote:
> Rich,
> Can I submit an issue and patch for this? I have a CA on file.
>
Sure, thanks.
Rich
> On Sun, Apr 5, 2009 at 8:15 PM, John D. Hume wrote:
>
>
>
> > Currently it does this:
> > (try
> > the good stuff ...
> > (catch Exception e
>
Rich,
Can I submit an issue and patch for this? I have a CA on file.
Thanks.
-hume.
On Sun, Apr 5, 2009 at 8:15 PM, John D. Hume wrote:
> Currently it does this:
> (try
> the good stuff ...
> (catch Exception e
> (.printStackTrace e *err*)))
> (flush))
>
> Instead I'd like it to:
I have experienced this as well. My problem is that I would like my test suite
to exit
the proper way
so that CI knows that the build actually failed. Currently test-is seems to
just report
to stdout, but
not set anything that would cause the suite to fail with the proper exit code.
Any ide
I'd like to second this request. It's pretty necessary to have an exit
code for any type of scripting.
Of course, you can always use (System/exit result-code), but a return
value is "prettier" to me.
On Apr 5, 5:15 pm, "John D. Hume" wrote:
> Earlier today I was surprised to notice that some te
Earlier today I was surprised to notice that some test-is unit tests I
was running from Ant failed, but it still reported BUILD SUCCESSFUL. I
figured I'd forgotten to include failonerror="true" in the java task,
but it was there. So I played around and found that
$ java -cp clojure.jar clojure.ma
