Open jpraet opened 1 year ago
Can you copy-paste the proxy part of your ~/.m2/settings.xml
? Obviously replace sensitive info with foo
, but include enough so we can have a testcase for parser.
Equo makes its network requests like so:
Not sure how to pass proxy information from your settings.xml
through to those clients, we might need to merge a PR into the EquoIDE project too...
<proxies>
<proxy>
<id>http-proxy</id>
<active>true</active>
<protocol>http</protocol>
<username/>
<password/>
<host>proxyapp.acme.com</host>
<port>8080</port>
<nonProxyHosts>localhost|*.acme.inet|10.*.*.*|192.168.*.*</nonProxyHosts>
</proxy>
</proxies>
Regarding proxy configuration in mvn
plugins:
I just ran into the same thing as reported here. Please note in my case, I never had the proxy settings in my settings.xml
as the plug-in is honoring my environment variables of HTTP_PROXY, HTTPS_PROXY, and NO_PROXY thus it should continue to do so.
This seems to have been broken since 2.34.0
as I went back to 2.33.0
and it worked just fine.
Is there any update on this? This blocks us from using the latest spotless version - with additional troubles downstream.
For instance the appears to be an issue when configuring the older spotless version for eslint/prettier with recent versions of those packages. This leads to certain files becoming corrupted during spotless-eslint/prettier.
We are having this issue also at my company.
Since the upgrade from spotless-maven-plugin 2.34.0 to 2.35.0 I get a "java.net.SocketTimeoutException: Connect timed out" (see full stacktrace below).
It looks like it's not respecting the configured proxy settings in my ~/.m2/settings.xml.
When I manually specify the proxy via the -Dhttps.proxyHost and -Dhttps.proxyPort system properties, it works.
Stacktrace: