win10 china(中国)
jdk 1.8
mvn test
--
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
Some of them look like stack traces were omitted by the jvm resulting in nil
traces. Some of the string stuff might be encoding issues?
--
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
Trying to re-acquaint myself with clojure since 1.6.0. Given *hosehead.clj*
as
(println (+ 1 2 3))
I used to be able to run:
% java -jar clojure-1.6.0.jar hosehead.clj
6
But with *clojure-1.9.0.jar* I'm treated to a *FileNotFoundException*
looking for *clojure/spec/alpha.clj* in the classpath
If you want to file a ticket in jira I’m happy to look at making the tests more
environment-independent (but I think that’s all this is).
--
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
No
Hey Payter,
As of Clojure 1.9, parts of Clojure have been pulled out into other repos. The
readme has instructions at the top for building a combined local jar from the
git repo:
https://github.com/clojure/clojure/blob/master/readme.txt
Or you can use the new Clojure runner clj described at:
true
UTF-8
after add propertis utf 8 to pom.xml , Still the same.
--
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 pa
Alex,
Thanks for the links.
Digging into the release notes for 1.9.0, I see that:
Note that spec is in alpha state and API compatibility is not guaranteed.
Also, spec and the specs for the Clojure core API are distributed as
external libraries that *must be included to use Clojure*.
Emphasis mi
Just another data point.
I tried Windows 10 Enterprise, Oracle JDK 1.8.0_171, Maven 3.5.0,
unmodified latest Clojure source code 1.10.0-alpha6.
mvn clean test
gave no errors. The language/system/internationalization settings were US
English, but I have no idea if that could be making a differen
We have begun the process of breaking Clojure into more fine-grained modules.
There is no timeline for this work but we expect this to become more common in
the future so we have no plans to change this aspect of packaging.
The major benefit is that the modules can be released independently and
On 25 Jul 2018, at 4:18, 冯忠孝 wrote:
> UTF-8
Is the build for this still using clojure-maven-plugin - it's possible I don't
propagate this field down into anything that would be used by clojure when
reading the CLJ files.
Does clojure have a property one can set to control the reader encodi
On Tuesday, 24 July 2018 05:53:03 UTC+1, 冯忠孝 wrote:
>
> [java] Ran 635 tests containing 17442 assertions.
> [java] 10 failures, 0 errors.
>
> I see Throwable->map is involved in all of these; but I can't see how it
could give the results it seems to here.
If you do
(Throwable->map (Excep
Mark, the Clojure build itself does not and has never used
clojure-maven-plugin. Clojure just inherits Java defaults for the default
encoding.
On the elided stack traces, the JVM is allowed to do this unless you pass a
flag telling it not to.
What kind of JDK is this? I’ve seen some weird stu
(def rechargecardflowname "rechargecard")
(def rechargedirectflowname "rechargedirect")
(def procurementstockflowname "procurementstock")
(defn abolish-name [flowname]
(str "abolish1" flowname)
)
(defn report-rechargecard [billid]
)
(defn consume-msg [msgname billid]
(case msgname
re
(Throwable->map (Exception. "text"))
=>
{:cause "text",
:via [{:type java.lang.Exception, :message "text", :at
[skyapi.core$eval49477 invokeStatic "form-init4673008911594595642.clj" 1]}],
:trace [[skyapi.core$eval49477 invokeStatic
"form-init4673008911594595642.clj" 1]
[skyapi.core$eva
As its docstring states, the `case` macro doesn't evaluate its test-constants.
It only works on compile-time constants (e.g. literal strings/numbers), to
allow O(1) matching. You want `condp` instead.
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
15 matches
Mail list logo
