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

can not use explict repo in offline mode when coursier cache has only POM file #3021

Closed
bishabosha opened this issue Jul 11, 2024 · 1 comment · Fixed by #3029
Closed

can not use explict repo in offline mode when coursier cache has only POM file #3021

bishabosha opened this issue Jul 11, 2024 · 1 comment · Fixed by #3029
Assignees
Labels
blocked upstream Issues and changes blocked by something in an external project. bug Something isn't working coursier Issues tied with coursier integration. installation Everything related to installing the CLI itself isolated environments Issues tied with running the CLI in isolated (or corporate) environments. SIP-46 All the issues related to SIP-46 to turn Scala CLI into the official scala runner command.

Comments

@bishabosha
Copy link
Contributor

bishabosha commented Jul 11, 2024

Version(s)
1.4.0 (problematic in scala 3.5.0-RC3 release when installing from cs install scala:3.5.0-RC3)

Describe the bug
in offline mode, If the coursier cache is only partially populated by POM, and no jar file (such is the state after running the cs install command) - then any explicitly added local repository is ignored and classpath resolution fails

To Reproduce
follow steps in coursier/coursier#3024

Expected behaviour
I have passed an explicit repo in offline mode, I expect to resolve the classpath from there, the fact that coursier complains underneath is a leaky abstraction.

@bishabosha bishabosha added the bug Something isn't working label Jul 11, 2024
@Gedochao Gedochao self-assigned this Jul 11, 2024
@Gedochao Gedochao added the SIP-46 All the issues related to SIP-46 to turn Scala CLI into the official scala runner command. label Jul 11, 2024
@Gedochao
Copy link
Contributor

Known workarounds:

  • remove the Scala compiler pom from Coursier cache (or just purge the cache)
  • pass an empty directory in the COURSIER_CACHE env variable

@Gedochao Gedochao added installation Everything related to installing the CLI itself isolated environments Issues tied with running the CLI in isolated (or corporate) environments. coursier Issues tied with coursier integration. blocked upstream Issues and changes blocked by something in an external project. labels Jul 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
blocked upstream Issues and changes blocked by something in an external project. bug Something isn't working coursier Issues tied with coursier integration. installation Everything related to installing the CLI itself isolated environments Issues tied with running the CLI in isolated (or corporate) environments. SIP-46 All the issues related to SIP-46 to turn Scala CLI into the official scala runner command.
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

2 participants