npen opened a new issue, #2139: URL: https://github.com/apache/maven-resolver/issues/2139
### Affected version 3.9 ### Bug description Following issue https://github.com/apache/maven-resolver/issues/997 resolution, it is possible to use aether.connector.http.useSystemProperties=true to allow the use of proxyHost and proxyPort system properties. However, the call to setDefaultCredentialsProvider which happens just before will lead to completely ignore the related authentication properties https.proxyUser and https.proxyPassword. I know using system properties is discouraged, here is my use-case: Running Claude Code in sandboxed mode on MacOS X, command run by Claude has to go through a proxy whose parameters (host, port, user and password) are available in environment variable HTTPS_PROXY. It's worth to note that those parameters are not fixed and change on every sessions. In the end, Claude ends up debugging maven commands, and duplicate settings.xml with proxy config added, and additional parameters to mvn commands. I tried to setup a simple .mavenrc file to declare correct MAVEN_OPTS dynamically based on HTTPS_PROXY variable. This works fine, except that https.proxyUser and https.proxyPassword are completely ignored, leading to HTTP 407 errors. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
