Mendix not using Proxy settings in gradle.properties
0
Dear Community,I am facing an issue where a proxy is configured in gradle.properties usingsystemProps: systemProp.http.proxyHost=proxy.example.com systemProp.http.proxyPort=8080 systemProp.https.proxyHost=proxy.example.com systemProp.https.proxyPort=8080 Running the Gradle build manually from the /deployment folder works perfectly,because it reads these settings from %USERPROFILE%\.gradle\gradle.properties.But Studio Pro's own dependency synchronization does NOT read this file andkeeps failing with: > Could not GET 'https://repo.maven.apache.org/maven2/.../cyclonedx-core-java-9.0.5.pom'. > (certificate_unknown) PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target Environment: Studio Pro 10.18, 10.24 and 11.6 (all Windows), Java 21, mandatorycorporate proxy (direct internet access is blocked).What I already verified:- Not a certificate problem: default cacerts is intact, no TLS interception (the proxy presents the normal public cert).- It's a proxy-reachability issue: keytool -printcert -sslserver repo.maven.apache.org:443 fails (no handshake), but with -J-Dhttps.proxyHost=proxy.example.com -J-Dhttps.proxyPort=8080 it immediately returns a valid certificate. So host/port are correct - the sync just goes out directly without the proxy.- Could NOT get the proxy into Studio Pro's Gradle/daemon process via net.properties, GRADLE_OPTS or JAVA_TOOL_OPTIONS (restarted Studio Pro and stopped the daemon each time).My question: how is the proxy supposed to be configured for Studio Pro's internalGradle dependency synchronization, so that it actually reaches the sync/daemonprocess? Is there a supported way that does not rely on ~/.gradle/gradle.properties?Thanks in advance!
asked
Benedikt Karl
1 answers
1
Hello Community,
I have figured out a fix that works in my environment. It turns out that in my settings.gradle, the truststore was also configured with these keys: