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.

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

yarnDownloadRoot looking at wrong location to download the package #601

Open
vediga opened this issue May 10, 2017 · 8 comments
Open

yarnDownloadRoot looking at wrong location to download the package #601

vediga opened this issue May 10, 2017 · 8 comments

Comments

@vediga
Copy link

vediga commented May 10, 2017

I am trying install node and yarn from intranet. Node gets installed fine but yarn fails to install as it could not download the package on the intranet

I have set
<yarnDownloadRoot> path/to/root/yarn/-/ </yarnDownloadRoot>

and the plugin tries to download yarn from path/to/root/yarn/-/v0.17.10/yarn-v0.17.10.tar.gz and gets a 404 but actually the package is located at path/to/root/yarn/-/yarn-v0.17.10.tar.gz

Please suggest a way to fix this.

@eirslett
Copy link
Owner

Try to move it on the intranet, so that it's in the correct place?

@vediga
Copy link
Author

vediga commented May 10, 2017

Is there a way I can specify absolute download path as opposed to specifying download root ?

@eirslett
Copy link
Owner

No, that's not possible.

@mtz
Copy link

mtz commented Jun 2, 2017

i have the same problem. the plugin is extending the path to path/to/root/yarn/-/v0.xx.xx/yarn-v0.xx.xx.tar.gz.

another problem is the fileending. the plugin trying to fetch *.tar.gz but i have *.tgz packages only available at intranet.

please provide an configuration option!

thanks in advance
mtz

@rbirkgit
Copy link

I have the same issue :(

@64BitAsura
Copy link

Please understand we are developer, fighting with devops isnt where send our productivity. @eirslett please give us release where we can specify yarn or any package absolute location inside config of pom :)

@AndreyEmelyanenko
Copy link

This problem is still super actual! Are there any improvement or life-hacks?

@eirslett
Copy link
Owner

There are 2 possible suggesions that don't involve ops teams:

  1. Just use npm - it has improved a lot since yarn came out. (Unless you really need the yarn-specific features)
  2. Download yarn and commit it into your git repository - it's a couple of MBs, but within reason. @AndreyEmelyanenko I think this would classify as a life hack?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants