(2/7) By the way, do try the Maven export when you have the time! ⚡
Life's that much easier when one doesn't have to write the pom.xml on their own. Just keep in mind it's still an experimental feature (and awaits your feedback!)
(3/7) JMH benchmarking has received some improvements as well (but is still an experimental feature as well). Benchmarks can now be controlled with dedicated using directives as well as command line options.
(4/7) They're also now supported in multiple sub-commands (and not just run, so you can compile your project separately, for example). Importing a benchmarking project to an IDE is now also supported.
More changes coming soon!
(5/7)It is now possible to launch an app with Scala CLI by just specifying its dependency, without the need to provide any source files. 🚀
There's also no need to specify the main class, as it's now being detected automatically in dependencies as well.
(6/7) This can be used similarly to Coursier's cs launch. Just do note that explicitly calling the run sub-command is necessary here, as otherwise Scala CLI will default to the REPL.
(7/7) For more details about all the features and fixes included in Scala CLI 1.5.0, check out the release notes https://github.com/VirtusLab/scala-cli/releases/tag/v1.5.0.
We're thrilled to announce the release of Scala CLI v1.5.0!
It's quite feature packed, including:
• support for Scala 3.5.0 and Scala Native 0.5.5
• auto-completions for fish shell user
• ( experimental) export to Maven
• ( experimental) improvements to JMH benchmarking 👇