proxy not forwarded to NPM

[geoHeil]

When using your plugin for an existing repository in a corporate setup behind a proxy it fails choose the proxy for downloading the node version.

to reproduce

git clone https://github.com/apache/ambari.git
cd ambari
mvn package

The log shows:

 Installing node version v4.5.0
[INFO] Downloading https://nodejs.org/dist/v4.5.0/node-v4.5.0-linux-x64.tar.gz to /home/vagrant/.m2/repository/com/github/eirslett/node/4.5.0/node-4.5.0-linux-x64.tar.gz
[INFO] No proxies configured
[INFO] No proxy was configured, downloading directly

and fails to download even though HTTPS_PROXY / HTTP_PROXY are set correctly.

The pom.xml ignores the proxy, but should foraward the HTTP(S)_PROXY environment variable to npm:

<configuration>
    <npmInheritsProxyConfigFromMaven>false</npmInheritsProxyConfigFromMaven>
</configuration>

[geoHeil]

Possible duplicate of #430

[Cavva79]

try my fix in #683
It passes HTTPS_PROXY, HTTP_PROXY as environment variables

[Cavva79]

@geoHeil have you solved this problem?

[geoHeil]

No Davide Cavarretta <notifications@github.com> schrieb am Di. 8. Mai 2018 um 09:11:

…

@geoHeil <https://github.com/geoHeil> have you solved this problem? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#700 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABnc9LWVJp6pqmUJpyevSjfvbGRpgG5Dks5twUTwgaJpZM4ScSKc> .

[8acker]

I had a similar issue and by providing the maven args -DproxyHost=proxy.url -DproxyPort=3128 it worked for me

[ironijunior]

I also have a similar problem.
The solution proposed by @tb0uchnafa didn`t work here, unfortunately. I hope #683 can fix it.