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

converter ignores custom ivy cache setting in sbt #156

Closed
an-tex opened this issue May 22, 2020 · 2 comments · Fixed by #162
Closed

converter ignores custom ivy cache setting in sbt #156

an-tex opened this issue May 22, 2020 · 2 comments · Fixed by #162

Comments

@an-tex
Copy link
Contributor

an-tex commented May 22, 2020

When running sbt -Dsbt.ivy.home=customCacheFolder this setting is not being used for the artifacts generated by the converter, instead the default $HOME/.ivy2/local is used.

This leads to assembly errors, e.g.

[error] sbt.librarymanagement.ResolveException: Error downloading org.scalablytyped:fortawesome__free-brands-svg-icons_sjs0.6_2.12:5.13.0-e66cf0
 [error]   Not found
 [error]   Not found
 [error]   not found: /builds/XXX/default/sbt-cache/ivy/local/org.scalablytyped/fortawesome__free-brands-svg-icons_sjs0.6_2.12/5.13.0-e66cf0/ivys/ivy.xml

This setting can be read from ivyPaths.value.ivyHome

In my case I'm using a gitlab runner with cached folders to speed up runs, but the cached folder must reside inside the cloned repo (and not in users home).

@oyvindberg
Copy link
Collaborator

Aha! I had a feeling this might show up, since I was too lazy to figure out where sbt found that. Would you mind giving it a shot with a PR? Start here probably https://github.com/ScalablyTyped/Converter/blob/master/sbt-converter/src/main/scala/org/scalablytyped/converter/plugin/ScalablyTypedConverterPlugin.scala#L106 and similar for ScalablyTypedConverterExternalNpmPlugin.scala

@an-tex
Copy link
Contributor Author

an-tex commented May 22, 2020

Thanks for the directions, I’ll create a PR next week!

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

Successfully merging a pull request may close this issue.

2 participants