Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Maven proxy settings are incorrectly passed to yarn
See original GitHub issueVersion 1.6
Relates to issue #660
frontend-maven-plugin calls yarn with:
yarn run build-prod --https-proxy=http://proxy:8080 --proxy=proxy:8080
Causing:
[ERROR] Unknown option: '--https-proxy'
[ERROR] Unknown option: '--proxy'
I think it should be:
yarn --https-proxy=http://proxy:8080 --proxy=proxy:8080 run build-prod
Issue Analytics
- State:
- Created 5 years ago
- Reactions:5
- Comments:6
Top Results From Across the Web
Maven proxy settings not working - Stack Overflow
I'm not able to do this with MVN 3.0.4 but I do with 3.0.3. It seems to be a bug in the 3.0.4...
Read more >Configuring a corporate proxy - JHipster
When JHipster is used in a company, you probably will need to configure all tools to bypass the corporate proxy. You can try...
Read more >How to resolve NPM proxy issue whilel running node JS ...
is a problem related to network connectivity. npm ERR! network In most cases you are behind a proxy or have bad network settings....
Read more >Guide to using proxies - Apache Maven
You can configure a proxy to use for some or all of your HTTP requests with Maven. The username and password are only...
Read more >Known Issues in MapReduce and YARN | CDP Private Cloud
That can cause problem when you want to switch between resource allocation modes, for example from weight mode to relative mode. The YARN...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
problem also exists in version 1.12.1. Would be great to have a solution for this.
It is not - and the PR is also still open. @eirslett any means to fix this issue from the plugin side?