0.19.1 cannot run on java 8 due to UnsupportedClassVersionError

[Elvis5566]

Do we need to upgrade jre11 to use slick-pg?
thanks

java.lang.UnsupportedClassVersionError: com/github/tminglei/slickpg/PgGeographyTypes$Geography has been compiled by a more recent version of the Java Runtime (class file version 55.0), this version of the Java Runtime only recognizes class file versions up to 52.0

[tminglei]

Well, sorry! Wrongly transferred to java 11 on local when trying to resolve not found: value getClass because of scala/scala#8541, and then released it.
I'll downgrade it and release a new version again.

[tminglei]

@Elvis5566 resolved. Pls use v0.19.2 instead.

[dhoepelman]

Unfortunately we are getting this error when trying to upgrade from 0.19.0 to 0.19.2.
Could it be that the JTS 0.19.2 module is still compiled with JDK11?

$ sbt "dependencyList" | grep pg
[info] com.github.tminglei:slick-pg_2.13:0.19.2
[info] com.github.tminglei:slick-pg_core_2.13:0.19.2
[info] com.github.tminglei:slick-pg_jts_2.13:0.19.2
[info] com.github.tminglei:slick-pg_play-json_2.13:0.19.2
$ sbt test | grep java.lang.UnsupportedClassVersionError
java.lang.UnsupportedClassVersionError: com/github/tminglei/slickpg/PgGeographyTypes$Geography has been compiled by a more recent version of the Java Runtime (class file version 55.0), this version of the Java Runtime only recognizes class file versions up to 52.0

[dhoepelman]

Yep, confirmed it by manually inspecting the class file.
Note the header starts with cafe babe 0000 0037, the 0x37 byte corresponds to decimal 55 or JRE 11

$ wget https://repo1.maven.org/maven2/com/github/tminglei/slick-pg_jts_2.13/0.19.2/slick-pg_jts_2.13-0.19.2.jar
$ unzip slick-pg_jts_2.13-0.19.2.jar
$ cat com/github/tminglei/slickpg/PgGeographyTypes\$Geography.class | xxd | head -n 1
00000000: cafe babe 0000 0037 000c 0700 0707 000a  .......7........

[tminglei]

@dhoepelman yeah, slick-pg_jts and slick-pg_jts_lt are still built for Java 11. Others look well.
Don't know why. But I'll rebuild again.

[tminglei]

@dhoepelman resolved. pls turn to use v0.19.3.

[dhoepelman]

0.19.3 solves the problem, thanks!