FYI - I fixed this by explicitly setting JAVA_HOME to point to my jdk1.8
directory.
On Sun, Mar 22, 2020 at 10:24 PM Reuven Lax wrote:
> Has anyone resolved this? I'm also getting this when I try to build from
> the console, though building from IntelliJ works fine. I need to run
> spotbugs thou
Has anyone resolved this? I'm also getting this when I try to build from
the console, though building from IntelliJ works fine. I need to run
spotbugs though, and I'm not sure how to do that from IntelliJ.
On Thu, Mar 12, 2020 at 3:31 PM Kyle Weaver wrote:
> I'm trying to set up Beam from scratc
I'm trying to set up Beam from scratch on a new Linux install, and I ran
into the same issue. Initially, I had my Intellij project set up with JDK
11, but when I tried switching to JDK 8 got the same error. When I run the
same Gradle command in the terminal, though, it worked. So I figure it must
b
Hi,
AFAIR I had the same issue on my Linux.
Let me do a new run.
Regards
JB
> Le 7 févr. 2020 à 21:35, Kenneth Knowles a écrit :
>
> The expected class file version 53 is for Java 9, I believe. So is the right
> javac being invoked?
>
> I hit some issues like this on mac a while back, unrel
The expected class file version 53 is for Java 9, I believe. So is the
right javac being invoked?
I hit some issues like this on mac a while back, unrelated to Java 11.
Suspected something wonky in Mac's Java setup not working well with the
Gradle wrapper. Never resolved them actually. Have been w
HiNo jdk 11 is not yet fully supported.I?ve started to work on it but it?s not yet ready.RegardsJBLe ven. 7 f?vr. 2020 ? 20:20, David Cavazos a ?crit :Hi Beamers,I'm trying to run the tests for the Java examples using Java 11 and there is a compilation error due to an incompatible version.I'm usin