-
Notifications
You must be signed in to change notification settings - Fork 94
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
Made Java installation as connection features #2283
Conversation
Signed-off-by: Seb Julliand <[email protected]>
Signed-off-by: Seb Julliand <[email protected]>
Signed-off-by: Seb Julliand <[email protected]>
Beautiful code change. Will get it tested ASAP. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think my only concern is the finding of JDK version without reloading. Other than that, very nice change!
Co-authored-by: LJ <[email protected]>
@worksofliam Can you try again? I connected to an existing system created and connected before the PR, and the reloading occurred as expected. The existing test was accurate: Or am I missing something obvious? 😅 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@sebjulliand Tested again and it worked as expected. I connected to an existing system and it grabbed the JDK correctly. Thanks!
Merge away!
Changes
This PR takes the Java discovery part of #2195.
The different possible Java installation locations are made into connection features.
These features are now used to get Java Home path when configuring the debug service.
How to test this PR
Checklist