Affected version
Bug description
Despite dozens of community discussions claiming otherwise on Reddit, Stack Overflow, old Apache bug trackers, and new GitHub Apache bug trackers, neither Maven nor Maven Wrapper support .mvn/jvm.config nor environment variables for simple proxy configuration.
None of the industry standard mechanisms available to Gradle, to other programming languages, to Ant, work in v3 Maven.
- Industry standard, cURL based environment variables:
http_proxy, http_proxy, no_proxy
- UPPERCASE environment variables:
HTTP_PROXY, HTTPS_PROXY, NO_PROXY
- Maven wrapper
.mvn/jvm.config files
- Maven's environment variables:
MAVEN_ARGS, MAVEN_OPTS
- JVM standard
JAVA_OPTS environment variable
As a workaround, settings.xml can be hardcoded to apply a proxy configuration. But this makes it significantly harder to override partial Maven configurations, compared with environment variables.
Affected version
Bug description
Despite dozens of community discussions claiming otherwise on Reddit, Stack Overflow, old Apache bug trackers, and new GitHub Apache bug trackers, neither Maven nor Maven Wrapper support
.mvn/jvm.confignor environment variables for simple proxy configuration.None of the industry standard mechanisms available to Gradle, to other programming languages, to Ant, work in v3 Maven.
http_proxy,http_proxy,no_proxyHTTP_PROXY,HTTPS_PROXY,NO_PROXY.mvn/jvm.configfilesMAVEN_ARGS,MAVEN_OPTSJAVA_OPTSenvironment variableAs a workaround,
settings.xmlcan be hardcoded to apply a proxy configuration. But this makes it significantly harder to override partial Maven configurations, compared with environment variables.