-
-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
ZAP 2.14.0 installer on Windows have misleading text when asking for Java Runtime Environment #8355
Comments
Where's the misleading text? |
And where did you download ZAP From? |
Downloaded from https://www.zaproxy.org/download/ |
From https://www.java.com/en/download/help/whatis_java.html
|
No, the JRE is more than enough to run ZAP as long as it is 11+. We do not recommend downloading from |
aha, thank you! Sorry for the confusion. |
Closing as this is now clarified. |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Describe the bug
When trying to install on Windows I got asked if I could point to the location of Java.
As I didn't have Java installed I went to https://www.java.com/en/download/ and downloaded the latest version ( jre-8u401-windows-x64).
I found it a bit weird that ZAP asked for minimum version of 11, when the latest is version 8.
Then selecting the java.exe did not work.
Only after I came across this post https://stackoverflow.com/a/75093390/5918611 and installed the latest OpenJDK, would the installer succeed.
I'm sure that this issue is trivial for anyone who have done any development in Java, but I found it confusing. I see that similar issues have been raised before as well: #6122
Steps to reproduce the behavior
Install ZAP without Java on Windows
Expected behavior
I would expect an error message that the describes what is needed to fix the problem.
Software versions
ZAP 2.14.0
Screenshots
No response
Errors from the zap.log file
No response
Additional context
No response
Would you like to help fix this issue?
The text was updated successfully, but these errors were encountered: