Hi @cmei84,
thanks for getting back to me. This is great news, that the issue was due to external software.
I think I can also provide you with some information here to sort out misconceptions:
- SonarLint for Eclipse coming bundled with its own Java 17 JRE is only been done since version 10.0, therefore you might not have faced any issues regarding certificates with previous versions
- Since SonarLint for Eclipse 10.0 the embedded JRE is used to run parts of the plug-in out of process any certificates required to your “normal” Java installation have to also apply to the certificate store of this JRE. But …
- … we also give you the option to instead of using the embedded JRE, you can just provide your own one that you have full control over. Please see my answer to a different post where similar environments required such changes.
- The documentation for this can be found HERE as well. This will also enable you to use your Java 17+ runtime while jumping between SonarLint versions if you want to update often but don’t want to configure the certificates every time. Or if it is managed by your organization.
If you encounter anything else that is not working, don’t hesitate to reach out in a new thread.
All the best,
Tobias