I am pretty sure I'm using Java 8. I do have both Java 8 and Java 11 installed, but the environment it's built with:
$ java -version java version "1.8.0_162" Java(TM) SE Runtime Environment (build 1.8.0_162-b12) Java HotSpot(TM) 64-Bit Server VM (build 25.162-b12, mixed mode) $ echo $JAVA_HOME /Library/Java/JavaVirtualMachines/jdk1.8.0_162.jdk/Contents/Home Same environment, just changing Clojure versions. I assume there's a change between Clojure 1.9 and 1.10 Java interop that explains the difference in behaviour? But AOT'ing using the wrong version of Java and deploying backwards certainly seems like it fits the problem perfectly, given the change in ByteBuffer between 8 and 9. Will further investigate. Cheers. And thanks, Alex. On Wednesday, January 16, 2019 at 11:37:00 PM UTC+10:30, Alex Miller wrote: > > Are you absolutely sure you’re not compiling on Java 9? I think Java 9 > added a position on ByteBuffer with covariant return (other versions have > it on the Buffer super class). > > From the error it looks like AOT compilation found the method and compiled > it into the byte code, but then that method is not found at runtime. I > think from eyeballing things (didn’t try it) that compiling with Java 9 and > running on Java 8 could result in this. -- 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.
