gnodet commented on issue #11011: URL: https://github.com/apache/maven/issues/11011#issuecomment-3386046193
This seems like a reasonable enhancement for cloud-native and CI/CD use cases where mounting a settings.xml file is less convenient. I'd suggest implementing this as a fallback mechanism: check for standard proxy environment variables (http_proxy/https_proxy, with lowercase taking precedence, then uppercase as fallback) and apply them as default proxies when no explicit proxy is configured in settings.xml for a given repository. Explicit settings.xml configuration would always take precedence. The main limitation is that environment variables would apply globally to all repositories, whereas settings.xml currently allows per-repository proxy configuration through <mirror> elements. However, this seems acceptable because users who need fine-grained control will continue using settings.xml, while the target use case (containers, CI/CD) typically wants a simple global proxy anyway. This would also align with conventions from other tools (curl, wget, apt, etc.) that respect these standard environment variables. @cstamas would you see any downside to this approach? -- 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]
