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

Unable to resolve scalaworker behind corporate proxy #187

Closed
GrannyOlli opened this issue Mar 2, 2018 · 4 comments
Closed

Unable to resolve scalaworker behind corporate proxy #187

GrannyOlli opened this issue Mar 2, 2018 · 4 comments
Labels
solved The issue was fixed/resolved
Milestone

Comments

@GrannyOlli
Copy link

In ScalaWorkerApi, resolving mill-scalaworker and compiler-interface from hard-coded repo1.maven.org fails behind a corporate proxy. It should be possible to configure a maven proxy for this.

https://github.com/lihaoyi/mill/blob/c5b967515cc4ccf6ebe76c69691c196b55113b3c/scalalib/src/mill/scalalib/ScalaWorkerApi.scala#L21

@lihaoyi
Copy link
Member

lihaoyi commented Mar 2, 2018

Yeah this is not currently possible, I have a commit in the test branch that will expose this as something you can configure

@lihaoyi
Copy link
Member

lihaoyi commented Mar 3, 2018

@GrannyOlli can you try using the latest unstable version https://github.com/lihaoyi/mill/releases/download/unstable/0.1.3-9-a6bd3d, instantiating a new mill.scalalib.ScalaWorkerModule in your build.sc with it's repositories overriden, and then overriding your scalaWorker in your ScalaModules to point towards your custom mill.scalalib.ScalaWorkerModule?

@GrannyOlli
Copy link
Author

Thank you, i will try that!

@lihaoyi
Copy link
Member

lihaoyi commented Mar 4, 2018

should be doable in 0.1.4

@lihaoyi lihaoyi closed this as completed Mar 4, 2018
shengc pushed a commit to shengc/mill that referenced this issue Mar 20, 2018
lihaoyi pushed a commit that referenced this issue Mar 20, 2018
lihaoyi pushed a commit that referenced this issue Mar 27, 2018
* doc to address #187 and #246

* add exclusions and custom configuration to dependencies and tests
@lefou lefou added this to the 0.1.7 milestone May 3, 2019
@lefou lefou added the solved The issue was fixed/resolved label Jul 3, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
solved The issue was fixed/resolved
Projects
None yet
Development

No branches or pull requests

3 participants