[
https://issues.apache.org/jira/browse/HDDS-13812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Andika updated HDDS-13812:
-------------------------------
Description:
Encountered build failure when proxy is specified in settings.xml
{code:java}
[ERROR] Failed to execute goal
com.github.eirslett:frontend-maven-plugin:1.15.4:pnpm (set [email protected] store
path) on project ozone-recon: Failed to run task: 'pnpm config set store-dir
~/.pnpm-store --https-proxy=http://localhost:9876 --proxy=http://localhost:9876
--noproxy=*.com,*.org' failed. org.apache.commons.exec.ExecuteException:
Process exited with an error: 1 (Exit value: 1) -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please
read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
{code}
HDDS-3913 already set npmInheritsProxyConfigFromMaven to false to prevent this
issue. However, proxy args
(i.e.`--https-proxy=[http://localhost:9876|http://localhost:9876/]
--proxy=[http://localhost:9876|http://localhost:9876/]
--noproxy={*}.{*}com{*},{*}.org`) seem to be wrongly inherited. See
[https://github.com/eirslett/frontend-maven-plugin?tab=readme-ov-file#proxy-settings]
for more details.
I suspect there were some regressions that causes
npmInheritsProxyConfigFromMaven (and potentially other args) to be ignored.
was:
Encountered build failure when proxy is specified in settings.xml
{code:java}
[ERROR] Failed to execute goal
com.github.eirslett:frontend-maven-plugin:1.15.4:pnpm (set [email protected] store
path) on project ozone-recon: Failed to run task: 'pnpm config set store-dir
~/.pnpm-store --https-proxy=http://localhost:9876 --proxy=http://localhost:9876
--noproxy=*.com,*.org' failed. org.apache.commons.exec.ExecuteException:
Process exited with an error: 1 (Exit value: 1) -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please
read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
{code}
HDDS-3913 already set npmInheritsProxyConfigFromMaven to false to prevent this
issue. However, proxy args (i.e. --https-proxy=http://localhost:9876
--proxy=http://localhost:9876 --noproxy=*.com,*.org) seem to be wrongly
inherited. See
https://github.com/eirslett/frontend-maven-plugin?tab=readme-ov-file#proxy-settings
for more details.
I suspect there were some regressions that causes
npmInheritsProxyConfigFromMaven (and potentially other args) to be ignored.
> npmInheritsProxyConfigFromMaven configuration does not ignore proxy
> -------------------------------------------------------------------
>
> Key: HDDS-13812
> URL: https://issues.apache.org/jira/browse/HDDS-13812
> Project: Apache Ozone
> Issue Type: Bug
> Reporter: Ivan Andika
> Priority: Major
>
> Encountered build failure when proxy is specified in settings.xml
> {code:java}
> [ERROR] Failed to execute goal
> com.github.eirslett:frontend-maven-plugin:1.15.4:pnpm (set [email protected] store
> path) on project ozone-recon: Failed to run task: 'pnpm config set store-dir
> ~/.pnpm-store --https-proxy=http://localhost:9876
> --proxy=http://localhost:9876 --noproxy=*.com,*.org' failed.
> org.apache.commons.exec.ExecuteException: Process exited with an error: 1
> (Exit value: 1) -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please
> read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
> {code}
> HDDS-3913 already set npmInheritsProxyConfigFromMaven to false to prevent
> this issue. However, proxy args
> (i.e.`--https-proxy=[http://localhost:9876|http://localhost:9876/]
> --proxy=[http://localhost:9876|http://localhost:9876/]
> --noproxy={*}.{*}com{*},{*}.org`) seem to be wrongly inherited. See
> [https://github.com/eirslett/frontend-maven-plugin?tab=readme-ov-file#proxy-settings]
> for more details.
> I suspect there were some regressions that causes
> npmInheritsProxyConfigFromMaven (and potentially other args) to be ignored.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
