We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Describe the issue
We use graalvm as a JDK for building native applications.
The build happens in a container where we need to set a proxy, as general egress is blocked.
Using -Djava.net.useSystemProxies=true has no apparent effect when using graalvm. It works with "regular" JDKs.
The http[s].proxyHost/proxyPort counterparts fortunately work, so we can use those instead.
Steps to reproduce the issue
Hard to reproduce without setting up an external proxy.
Describe GraalVM and your environment:
More details
-XshowSettings shows that the setting of the property is registered. It just has no apparent effect.
The text was updated successfully, but these errors were encountered:
Thanks for reporting this issue. We will take a look into it and get back to you.
Sorry, something went wrong.
rodrigar-mx
No branches or pull requests
Describe the issue
We use graalvm as a JDK for building native applications.
The build happens in a container where we need to set a proxy, as general egress is blocked.
Using -Djava.net.useSystemProxies=true has no apparent effect when using graalvm. It works with "regular" JDKs.
The http[s].proxyHost/proxyPort counterparts fortunately work, so we can use those instead.
Steps to reproduce the issue
Hard to reproduce without setting up an external proxy.
Describe GraalVM and your environment:
More details
-XshowSettings shows that the setting of the property is registered. It just has no apparent effect.
The text was updated successfully, but these errors were encountered: