-
Notifications
You must be signed in to change notification settings - Fork 1.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
Avoid untrusted binary popups in vscode-java when using Lombok #19690
Comments
for vscode-java is done here: https://github.com/redhat-developer/vscode-java/blob/master/src/settings.ts#L141-L158 |
Filed issue in vscode-java: redhat-developer/vscode-java#1965 |
@ericwill And the current workaround for this is to click Allow in the Security Warning dialog box, correct? |
Correct. |
This may get fixed for vscode-java 0.82.0. I've proposed a solution where files outside of the workspace are exempt from the warning : redhat-developer/vscode-java#1965 (comment) |
depends on #20134 |
Note that in CRW 2.14 we will consume lombok 1.18.22 built from sources, rather than consumed as a 3rd party binary jar. https://github.com/redhat-developer/codeready-workspaces-images/blob/crw-2-rhel-8/codeready-workspaces-plugin-java8/build/build_lombok.sh Not sure if that makes it easier to excempt lombok from security warning. |
This should have also been fixed in redhat-developer/vscode-java#1965 (comment) (since v0.82.0). No prompt is shown if the path provided to |
Fixed by eclipse-che/che-plugin-registry#1060 |
Is your task related to a problem? Please describe.
Running the Lombok devfile will show a warning about trusting the binary:
Describe the solution you'd like
We should find a way to have this popup not appear, and the binary be trusted by default. The binary is installed in the sidecar at build time.
Describe alternatives you've considered
Additional context
This happens with vscode-xml as well: https://github.com/redhat-developer/vscode-xml/blob/master/src/server/binary/binaryServerStarter.ts#L166
The text was updated successfully, but these errors were encountered: