-
Notifications
You must be signed in to change notification settings - Fork 3.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Getting Started has error #3744
Comments
Yes the doc needs an update. |
Just ran into this. New laptop and JAVA/ANTLR were not installed. My guess is this is related to Oracle now charging for latest Java (since 2019). But Thats just a wild guess. |
may i submit a pull request |
Fixed by #3748 |
Wanted to let you know that I spent several hours trying to figure out how to get antlr4 to run on my Windows 10 machine. See my related SO question here. Tomorrow's chore is to figure out the antlr4 .jar interacts with the Python module, but, at least for today, I was able to get antlr4 running. I had to uninstall my latest version of Java and revert back to 11 for it to work. Otherwise I continually got the error referenced in this issue. |
FYI Java 1.8 is older than Java 11, so what you did is the opposite of what you think. You actually upgraded Java.
The issue is in the docs and already fixed.
Envoyé de mon iPhone
… Le 22 juil. 2022 à 03:55, TrekkieByDay ***@***.***> a écrit :
Wanted to let you know that I spent several hours trying to figure out how to get antlr4 to run on my Windows 10 machine. See my related SO question here.
Tomorrow's chore is to figure out the antlr4 .jar interacts with the Python module, but, at least for today, I was able to get antlr4 running. I had to uninstall my latest version of Java and revert back to 11 for it to work. Otherwise I continually got the error referenced in this issue.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.
|
Java 1.8 is equals to Java 8 Java version history |
I don't mean to argue... but no, I went from the current version of java (the one that is listed in green on the wikipedia page, Java SE 18) to Java SE 11 from 2018. That was the only way I could avoid the error. Perhaps there are later versions I could have used, but frankly at that point yesterday I was tired of experimenting and elated to find something that worked. I apologize if I don't quite understand the weird Java versioning scheme... but, to be clear, no. The latest version of java by the chart from Wikipedia that I'll link below, Java 18, was not compatible... at least on my machine with my environment... but Java 11 was. I went from the green highlighted one (i.e. current) to the one highlighted yellow that corresponds to September 2018. Sorry for the ambiguity. Edit: Now, it is completely possible that there was some weird quirk on my system... but, as I explain in my SO post, I tried uninstalling, reinstalling, triple checking path variables, and trying on two completely different machines. I don't, however, discount the possibility of being confused about something... you guys are a lot smarter on this than me. I was just trying to do my "civic duty" and let you know. 🤷 |
That is not what you wrote on SO and class version error you encountered definitely happens with 1.8 but not with 18
Envoyé de mon iPhone
… Le 22 juil. 2022 à 14:03, TrekkieByDay ***@***.***> a écrit :
I don't mean to argue... but no, I went from the current version of java (the one that is listed in green on the wikipedia page, Java SE 18) to Java SE 11 from 2018. That was the only way I could avoid the error. Perhaps there are later versions I could have used, but frankly at that point yesterday I was tired fo experimenting and elated to find something that worked. I apologize if I don't quite understand the weird Java versioning scheme... but, to be clear, no. The latest version of java, Java 18, was not compatible... at least on my machine with my environment... but Java 11 was. I went from the green highlighted one to the one highlighted yellow that corresponds to September 2018. Sorry for the ambiguity.
Java version image
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.
|
@TrekkieByDay you should learning something about java version, java 1.8 also called java 8 , but which is different with java 18 |
If you are interested, I can take more time to try to be a little more
precise and exact about my error and actually reproduce it. Otherwise, I'm
good to go and feel like I did my duty by letting you know what happened.
Was not meant to be any kind of disrespect or anything, I'm just trying to
get through a project 🙂
…On Fri, Jul 22, 2022, 8:35 AM ericvergnaud ***@***.***> wrote:
That is not what you wrote on SO and class version error you encountered
definitely happens with 1.8 but not with 18
Envoyé de mon iPhone
> Le 22 juil. 2022 à 14:03, TrekkieByDay ***@***.***> a écrit :
>
>
> I don't mean to argue... but no, I went from the current version of java
(the one that is listed in green on the wikipedia page, Java SE 18) to Java
SE 11 from 2018. That was the only way I could avoid the error. Perhaps
there are later versions I could have used, but frankly at that point
yesterday I was tired fo experimenting and elated to find something that
worked. I apologize if I don't quite understand the weird Java versioning
scheme... but, to be clear, no. The latest version of java, Java 18, was
not compatible... at least on my machine with my environment... but Java 11
was. I went from the green highlighted one to the one highlighted yellow
that corresponds to September 2018. Sorry for the ambiguity.
>
> Java version image
>
> —
> Reply to this email directly, view it on GitHub, or unsubscribe.
> You are receiving this because you commented.
—
Reply to this email directly, view it on GitHub
<#3744 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AC5IKBKA6QAKCK6GIJLQIB3VVKISZANCNFSM5YRUYNSA>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
I will go back and update my stack overflow with exactly what my post is
here, but the fact remains that I tried getting it to work with the latest
version of Java.... That is to say that I downloaded the version of Java
that was pointed to automatically by Oracle for the latest version.... It
didn't work.... And eventually I tried this version from 2018 and it did.
The error I was getting is the same class error that is mentioned in this
post. Like I said, I don't exactly know what that means, and I will grant
that. I haven't taken the time to give a complete error trace of my process
that I used, but at the very least seems like something is amiss.
…On Fri, Jul 22, 2022, 8:35 AM ericvergnaud ***@***.***> wrote:
That is not what you wrote on SO and class version error you encountered
definitely happens with 1.8 but not with 18
Envoyé de mon iPhone
> Le 22 juil. 2022 à 14:03, TrekkieByDay ***@***.***> a écrit :
>
>
> I don't mean to argue... but no, I went from the current version of java
(the one that is listed in green on the wikipedia page, Java SE 18) to Java
SE 11 from 2018. That was the only way I could avoid the error. Perhaps
there are later versions I could have used, but frankly at that point
yesterday I was tired fo experimenting and elated to find something that
worked. I apologize if I don't quite understand the weird Java versioning
scheme... but, to be clear, no. The latest version of java, Java 18, was
not compatible... at least on my machine with my environment... but Java 11
was. I went from the green highlighted one to the one highlighted yellow
that corresponds to September 2018. Sorry for the ambiguity.
>
> Java version image
>
> —
> Reply to this email directly, view it on GitHub, or unsubscribe.
> You are receiving this because you commented.
—
Reply to this email directly, view it on GitHub
<#3744 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AC5IKBKA6QAKCK6GIJLQIB3VVKISZANCNFSM5YRUYNSA>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Thanks for letting us know @TrekkieByDay |
i just run the test command
java org.antlr.v4.Tool
my java version is "1.8.0_291"
and the error is
Error: A JNI error has occurred, please check your installation and try again
Exception in thread "main" java.lang.UnsupportedClassVersionError: org/antlr/v4/Tool 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
this mean it does not support java earlier than jdk 11,
but your Getting Started with ANTLR v4 said just java version 1.7 or higher
The text was updated successfully, but these errors were encountered: