coursier VS sbt-assembly

This is an upstream page size issue, equivalent issue here: https://github.com/coursier/coursier/issues/2636

I feel like this is already is the case, one can use coursier https://get-coursier.io/ or scala-cli to get started with Scala extremely fast.

I had a nice workflow installing different Java versions using SDKMAN but switched to Coursier because that't what's recommended in the Almond installation guide. In order to run `jupter lab` and start up the notebook environment, I need to separately install Jupyter Lab via conda (and activate that conda environment).

Could a Java project use a similar scheme? Probably, but the practicality of that is dependent on programatic resolution tools like coursier which don't exist in a convenient form for Java programmers quite yet.

Shell for issuing SQL to relational databases via JDBCIf you have Coursier installed, you can quickly connect to a demo Hypersonic database with:

This seems the same thing: - https://github.com/oracle/graal/issues/4479 - https://github.com/coursier/coursier/issues/2395

I use coursier to install scala. https://get-coursier.io/

I'm digging a bit deeper on this Google Artifact Repository task and it looks like it won't. See https://github.com/coursier/coursier/issues/1987 for more details.

You may also use sbt-assembly to produce an uber JAR that embeds the Scala stdlib together with your code, which means that now for running your program you only need a JRE like java -jar app-assembly.jar. This option is great because now if you start adding dependencies to your project those are also included in this massive JAR.

Sbt-assembly defaults to silently concatenating configs. But even if it didn't, the configs wouldn't be in any particular order when resolving.

With the sbt-assembly plugin you can create JAR-files with all of its dependencies (fat JARs). sbt assembly creates this target/scala-2.12/apply-at-vdb-assembly-0.1.0-SNAPSHOT.jar which has a size of around 42MB: