-
Notifications
You must be signed in to change notification settings - Fork 133
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
Java Development Kit Required webview always showing #143
Comments
It looks like why this is happening is my JDK returns the following as its string from
This fails the regex that is being used. |
Thank you for your feedback and sorry about this case. A fix will be out next week to cover more JDK distributions correctly. |
Thanks. I guess maybe a bigger question is why isn't this extension just using the java home detection that the redhat extension exposes through it's extension API. That would give all the information required, make sure it's in sync, and reduce duplicated code. As an extension pack, this already has a dependency on that. All the other java extensions switched to use that API to reduce code duplication. |
I'm not aware of the extension API by Red Hat. Could you point me to that? |
https://github.com/Microsoft/vscode-java-debug/blob/master/src/utility.ts#L108 It exposes the java home it finds for other extensions, and leaves it undefined if a jdk is not found. This is the full API that is exposed |
I think that might be a better option. I'll open another PR to use that concept as well, that way you can choose which solution you like better. |
This is perfect. I'll try that too. |
I opened up both as PRs so you can try both easily. |
Ever since the update to 0.7.0, upon opening any Java project the Webview saying the JDK is required always pops up, even though my system has JDK 11 on it. The checkbox saying
Show overview page when using Java
is ignored as well.Environment
Steps To Reproduce
Current Result
The webview shows
Expected Result
No webview to show
Additional Informations
The intellisense works, so the webview is just being invasive, and is just wrong.
The text was updated successfully, but these errors were encountered: