This is indeed related to CLJ-2066 - the issue is the object that
data.xml is trying to reflect on is a SaxParserImpl, which comes from
a non-exported module in Java 9. The object implements SaxParser, and
parse() is a public method there, but Reflector is calling getClass()
on the object and tryin
Just upgraded from 0.0.8 to
[org.clojure/data.x
ml "0.2.0-alpha3"]
and am still getting the same error. The offending statement is
(clojure.data.xml/parse)
where the BIS is the result of
(clojure.java.io/input-stream
(clojure.java.io/resource ))
Alan
On Fri, Nov 3, 2017 a
I believe this is https://dev.clojure.org/jira/browse/CLJ-2066 which can
most easily be fixed by avoiding reflection. If this is happening from
data.xml, newer versions of that lib have fixed it I believe.
On Fri, Nov 3, 2017 at 3:36 PM, Alan Thompson wrote:
> OK, I upgraded lein to 2.8.1, and i
OK, I upgraded lein to 2.8.1, and it removed one of the error messages. I
still have one remaining:
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by clojure.lang.Reflector
(file:/home/alan/.m2/repository/org/clojure/clojure/1.9.0-beta4/clojure-1.
On Thursday, 2 November 2017 19:46:35 UTC, Alex Miller wrote:
>
> I think this is an issue with Leiningen with Java 1.9 (re things in
> dynapath and the changes in classloader details in Java 1.9), and not
> Clojure itself.
>
> Yes this was leiningen issue #2331 now fixed:
https://github.com/tec
I think this is an issue with Leiningen with Java 1.9 (re things in
dynapath and the changes in classloader details in Java 1.9), and not
Clojure itself.
On Thu, Nov 2, 2017 at 2:31 PM, Andy Fingerhut
wrote:
> Alan, I get similar messages when starting 'lein repl' with this
> combination of vers
Alan, I get similar messages when starting 'lein repl' with this
combination of versions:
+ Leiningen version 2.8.0, Clojure 1.8.0, Java 9.0.1 (note - No Clojure
1.9.0 involved)
Changing only the Leiningen to version 2.8.1 and there is no such error
message.
Andy
On Thu, Nov 2, 2017 at 11:29 AM,
Hi. 1.9.0-beta4 works great for the Tupelo library on java 1.8, but I get
the following warnings using Java 9.0.1:
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by dynapath.defaults$eval380$fn__381 to
method java.net.URLClassLoader.addURL(java.ne
>
> FWIW, bigdec? seemed to fit better, given bigdec as a coercion and
> BigDecimal as the underlying type – decimal? always seemed like the anomaly.
>
Thought so too, but since there's no small decimal, or any other decimal,
its survivable. Though it does get a bit confusing, especially since
Aside from needing to change bigdec? to decimal? in four places in our code,
testing with Beta 4 has not shown any problems so we’ll probably go to
production with it early next week.
FWIW, bigdec? seemed to fit better, given bigdec as a coercion and BigDecimal
as the underlying type – decimal?
10 matches
Mail list logo