Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Maven proxy settings are incorrectly passed to yarn #796

Open
Borewit opened this issue Feb 14, 2019 · 6 comments
Open

Maven proxy settings are incorrectly passed to yarn #796

Borewit opened this issue Feb 14, 2019 · 6 comments

Comments

@Borewit
Copy link

Borewit commented Feb 14, 2019 •
edited
Loading

Version 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
@Borewit Borewit mentioned this issue Feb 14, 2019
Open
Borewit added a commit to Borewit/frontend-maven-plugin that referenced this issue Feb 14, 2019
@Borewit
eirslett#796 Changed sequence of Yarn execution arguments, to make th…
b75aeb3 
…e proxy settings appear at the correct location.
@Borewit Borewit mentioned this issue Feb 14, 2019
Open
@OldIMP
Copy link

OldIMP commented Oct 8, 2019

same bug for npm

@phuongnq
Copy link

Do we have any update on this issue?

@phuongnq phuongnq mentioned this issue Feb 3, 2020
Merged
Borewit added a commit to Borewit/frontend-maven-plugin that referenced this issue Mar 11, 2020
@Borewit
eirslett#796 Changed sequence of Yarn execution arguments, to make th…
8ec1e05 
…e proxy settings appear at the correct location.
@mshepel
Copy link

mshepel commented Sep 8, 2021

It's resolved in version 1.12.0

@neloman3
Copy link

There is the same problem with npm but 1.12.0 seems to be already bad

@OmarHawk
Copy link

OmarHawk commented Feb 16, 2022 •
edited
Loading

It's resolved in version 1.12.0

grafik

It is not - and the PR is also still open. @eirslett any means to fix this issue from the plugin side?

@gstolz
Copy link

gstolz commented Mar 7, 2022

problem also exists in version 1.12.1. Would be great to have a solution for this.
Screenshot 2022-03-07 at 16 51 26

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
7 participants
@OmarHawk @phuongnq @gstolz @OldIMP @Borewit @neloman3 @mshepel