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

document Coursier cache location #5120

Open
eed3si9n opened this issue Sep 23, 2019 · 7 comments
Open

document Coursier cache location #5120

eed3si9n opened this issue Sep 23, 2019 · 7 comments

Comments

@eed3si9n
Copy link
Member

  1. csrCacheDirectory key,
  2. -Dsbt.coursier.home property
  3. COURSIER_CACHE environment variable
  4. Does old cache location ($HOME/.coursier/cache/v1) exist? If so, use it * subject to change
  5. What OS do you use? If it's Linux, $HOME/.cache/coursier/v1.
@mkurz
Copy link
Member

mkurz commented Oct 16, 2019

Highly needed.

@alexarchambault
Copy link
Contributor

FYI, the coursier web site has a page about it.

@mkurz
Copy link
Member

mkurz commented Oct 16, 2019

@alexarchambault Yeah, but it doesn't mention -Dsbt.coursier.home

@eed3si9n
Copy link
Member Author

Partly fixed by sbt/website#850

@dwijnand dwijnand added the area/library_management library management label Jan 4, 2020
ScalaWilliam added a commit to ScalaWilliam/coursier that referenced this issue Mar 21, 2021
coursier#1483

sbt/sbt#5120

Doing this as most users informing me about cache location confusion use Coursier through SBT, rather than standalone.
@ScalaWilliam
Copy link
Contributor

@mkurz mentioned in the PR coursier/coursier#2012

@ScalaWilliam
Copy link
Contributor

@eed3si9n Is there a reason why coursier keys start with csr as opposed to coursier? Thinking in terms of discoverability.

When I tried to find the cache directory key, I was typing coursier<TAB> and not finding it - then found it looking through SBT sources.

ScalaWilliam added a commit to ScalaWilliam/website that referenced this issue Mar 21, 2021
Related to sbt/sbt#5120

The `csr` key was not so obvious so should be mentioned in the docs.
@eed3si9n
Copy link
Member Author

When we implemented sbt 1.3.x people were using Coursier via sbt-coursier and I did not want the keys to clash.

alexarchambault pushed a commit to coursier/coursier that referenced this issue Mar 21, 2021
#1483

sbt/sbt#5120

Doing this as most users informing me about cache location confusion use Coursier through SBT, rather than standalone.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants