sbt-bintray VS coursier

At Semantic Scholar, we used Bintray for our scala libraries both internally and externally. Since it is shutting down, we're migrating to AWS CodeArtifact. To make that process as smooth as possible, I wrote an sbt plugin that aims to make it as easy to publish as the sbt-bintray plugin.

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/

If you truly must avoid it, then take a look at coursier and ammonite: https://get-coursier.io/ and cs launch com.lihaoyi:ammonite_2.13.1:2.0.4 -M ammonite.Main

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.