-
Notifications
You must be signed in to change notification settings - Fork 34
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
[suggestion] clarification of java branch #22
Comments
Thanks for the feedback, that is a very good point you're making and has been the main point of friction for users. |
I'm glad you take my point in the spirit it was intended, as I don't see you as being at fault. |
Sorry for the delay, I just packaged build 2.1.0 for windows, which has the right JRE embedded. |
The site and docs need more clarity
Saying "at least java 11" isn't as useful as it should be with other software.
Java versioning is a confusing landscape for the average user.
Most users are not developers so install the regular runtime files from https://www.java.com/en/download/manual.jsp
This is version 8 branch, so Visual Trace Route fails to run, shows an error and sends the user to the oracle site for a developer version of java.
Here we are presented with a myriad of options depending on where on the page you look.
Some may be free but the language it is not as clear as it could be.
The offered version are 17 and 20 with a perplexing end of life being reversed as the v17 will be updated longer than 20.
Once scrolling down the page we finally find version 11 and wonder if and why that lower number has a longer shelf life than both 17 and 20.
So in short some explanation to an average end-user, of the requirement of which version between SE, JDK, JRE is needed
This software will not work with the common regular newest end user java, but instead requires a specific developer branch.
The text was updated successfully, but these errors were encountered: