Pure Scala Artifact Fetching
APACHE-2.0 License
Bot releases are visible (Hide)
Published by alexarchambault about 4 years ago
javax.net.ssl.SSLHandshakeException
thrown when downloading things from github.com
from the native Windows launcherPublished by alexarchambault about 4 years ago
sbtn
to the default application list, installed during cs setup
cs install
and cs setup
(this has been a problem when installing cs
on Windows since 2.0.1
was tagged, when using the native launcher)cs install
(#1892, thanks to @Poorva17)Published by alexarchambault about 4 years ago
Published by alexarchambault about 4 years ago
No changes since 2.0.0-RC6-27
.
Published by alexarchambault about 4 years ago
arm
and aarch64
JVM architectures in the java
and java-home
commands (#1849, thanks to @matsluni)20.1.0
Java 11 (former coursier versions used GraalVM 19.3.1
Java 8)--jvm-index
option to the java
/ java-home
/ setup
commands, allowing to pass a custom JVM index URL, also accepting aliases such as jabba
(current default) and cs
(supporting less JVM flavors, but more up-to-date)20.1.0
and GitHub actions fixes the generation of native launchers on the CI, which should be shipped as GitHub release assets again (which was broken in 2.0.0-RC6-25
and 2.0.0-RC6-26
)Published by alexarchambault about 4 years ago
-J-D
in the native launcher (this can be useful for http proxies in particular){http,https}.proxyUser
and {http,https}.proxyPassword
Java properties, set up proxy authentication accordinglypowershell.exe
detection, use pwsh.exe
from Powershell >= 6.0 if needed)Published by alexarchambault about 4 years ago
info.*
attributes as properties when parsing ivy.xml
files (these attributes can include scaladoc links in particular, fixed in #1820, thanks to @eed3si9n)Published by alexarchambault about 4 years ago
latest.stable
doesn't match milestones or alpha / beta versions.COURSIER_REPOSITORIES
, so that Ivy repositories with different metadata and artifact patterns can be used.update
and list
command on Windows.fetch
command is empty.java
and java-home
commands, don't re-download JVM index when not necessary. (If the cached index has a matching JVM, it's used straightaway, and the index is not updated. Pass --update
to force updating the index.)gcs
, gcs-eu
, gcs-asia
)Published by alexarchambault over 4 years ago
IllegalArgumentException: toMillis not allowed
error, that can sometimes happen with infinite TTLs (which became the default from the CLI in 2.0.0-RC6-22
when an application rather than Maven coordinates is passed)Published by alexarchambault over 4 years ago
~/.coursier/cache
From version 2.0.0-RC6-14
up to 2.0.0-RC6-21
, the coursier CLI prints a warning if the legacy cache location (pre Nov 2017),
~/.coursier/cache
is being used, pointing to cache-migration to help migrate to the new cache location.. Support for ~/.coursier/cache
is now dropped altogether.
The configuration directory changed from
~/Library/Preferences/Coursier
to
~/Library/Application Support/Coursier
The latter is more correct per the Apple documentation, see the discussion here for more details.
The former location might be deprecated in a late future. Files there are still accepted for the time being.
Contents/Home
on macOS, so that cs java --jvm adopt:1.10.0-2 -version
now works.1.
prefix in JVM versions, which was faulty in some cases, so that cs java --jvm openjdk:10 -version
now works, in particular.get
commandPrints the path of a file in the coursier cache, downloading it if necessary. Use like
$ cs get https://repo1.maven.org/maven2/io/get-coursier/coursier-cli_2.12/2.0.0-RC6-21/coursier-cli_2.12-2.0.0-RC6-21.jar
/Users/alexandre/Library/Caches/Coursier/v1/https/repo1.maven.org/maven2/io/get-coursier/coursier-cli_2.12/2.0.0-RC6-21/coursier-cli_2.12-2.0.0-RC6-21.jar
In the java
and java-home
commands, when passing short versions like adopt:11
or graalvm:20
, if a valid JVM matching that version is already unpacked locally, it is used straightaway. In particular, if a newer matching version is available per the JVM index, the local one is still preferred. Pass --update
to force using the latest matching version from the index (former behavior).
In the java
and java-home
commands, if a valid JVM is available locally, it is used straightaway (see previous section), and no attempt is made to update the index. Previously, the index was updated if the last check was older than the TTL (24 hours by default). The index is now only checked when --update
is passed.
When passing applications to the resolve
, fetch
, launch
, or bootstrap
commands, like cs launch scala
, the TTL now defaults to Inf
(infinite). That means that if all the necessary files to start an application are in the cache, it is launched straightaway, even if a newer version could have been downloaded. Pass an explicit TTL value to recover the former behavior, like cs launch scala --ttl 24h
.
Published by alexarchambault over 4 years ago
--credentials
and --credentials-file
now don't require https by default, and are automatically tried when getting an authentication error on their host)--jvm-option-file .jvmopts
to the bootstrap
command to have the bootstrap read .jvmopts
if it exists)Published by alexarchambault over 4 years ago
jcenter
repository alias (use like cs resolve -r jcenter …
)cs setup
, rather than the non-standard coursier-based sbt-launcher
Published by alexarchambault over 4 years ago
cs list
doesn't crash if the app directory doesn't existexecve
works (should make launch
with explicit JVMs, like cs launch ammonite --jvm 11
, work)Published by alexarchambault over 4 years ago
-E
option) not excluding root dependencies themselves in the CLIexclude
node in Ivy XML filesPublished by alexarchambault over 4 years ago
Resolution
object to Resolve
(can be used to pass a Resolution
with pre-filled caches to speed things up, for example)Published by alexarchambault over 4 years ago
1.0.1
(from 0.6.32
)coursier.{Artifacts, Fetch}
Published by alexarchambault over 4 years ago
2.0.0-RC6-2
. Fixed in #1704, thanks to @jodersky.Published by alexarchambault over 4 years ago
~/.coursier/cache
This impacts users who used a coursier version released before Nov. 2017. These users should have a ~/.coursier/cache
directory on their disk. For these users, this directory should be picked as default cache directory most of the time, per the rules introduced along with the newer cache location.
As of this version, and until 2.0.0
final, running the coursier CLI will print a warning if ~/.coursier/cache
is found and used as default location per the rules picking the default cache location. That warning message points to the cache-migration
tool, that helps migrate ~/.coursier/cache
to the newer cache location.
You might have a ~/.coursier/cache
directory, and not get that warning. This happens when you first ran a post Nov. 2017 coursier version on your system, that created the OS-specific cache directory, then ran a pre Nov. 2017 one, that created a ~/.coursier/cache
nonetheless. You can run cache-migration
too, if you'd like to migrate what's under ~/.coursier/cache
to the newer cache.
Optimize some data structures used during resolution, thanks to @jtjeferreira.
Published by alexarchambault over 4 years ago
COURSIER_INSTALL_DIR
environment variable in the install
command (thanks to @zheh12)cs
is installed with cs install cs
or via cs setup
, running just cs
now prints the help like on Linux and macOS, instead of running the setup
commandPublished by alexarchambault over 4 years ago
list
command to list installed applications (thanks to @ckipp01)clojars
as a repository, pointing to Clojure's clojars