coursier VS sbt-native-packager

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.

once you outgrow scala-cli, you should know sbt has a lot of plugins ( some might say it's ecosystem is the only thing keeping it relevant....) like sbt-native-packager which again does the heavy lifting for you

You should use sbt-jib. (You shouldn't use sbt-native-packager either, it doesn't work well in this regard: [1], [2].)

IMO don't take any of this advice and use https://github.com/sbt/sbt-native-packager