[
https://jira.codehaus.org/browse/MNG-5247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=315094#comment-315094
]
Boni Gopalan edited comment on MNG-5247 at 12/6/12 12:10 AM:
-------------------------------------------------------------
since it is a JVM switch setting -Djava.net.useSystemProxies=true to MAVEN_OPTS
should make it work for all plugins (and anything else from within the code).
EDIT:
adding -Djava.net.useSystemProxies=true appended to MAVEN_OPTS did not work.
However clean install -Djava.net.useSystemProxies=true works well with proxy on
or proxy off. Surprised. I am sure I am missing something fundamental about
the way MAVEN_OPTS is interpreted. Is it to set only the -X parameters?
was (Author: devasur):
since it is a JVM switch setting -Djava.net.useSystemProxies=true to
MAVEN_OPTS should make it work for all plugins (and anything else from within
the code).
OOPS : Looks like there are more complications. Will work only for classes
using java.net.* for network access.
> be able to propagate the proxy from settings.xml to plugins
> -----------------------------------------------------------
>
> Key: MNG-5247
> URL: https://jira.codehaus.org/browse/MNG-5247
> Project: Maven 2 & 3
> Issue Type: New Feature
> Reporter: Romain manni-Bucau
> Attachments: MAVEN-PLUGINS-PROXY.diff
>
>
> can be nice if plugins could get proxies defined in settings.xml.
> for surefire a way to do it without modifying the plugin is to set proxy
> information in user properties (otherwise it doesn't work in forked mode)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira