Consider adding scala-cli as an alternative build tool #45

adamw · 2022-06-22T09:00:31Z

Could be a good fit a small, simple project?

https://scala-cli.virtuslab.org

Changes: * add builder parameter with default value Sbt to both request and model objects * identify Sbt related classes/methods/members and add 'sbt' infix to them Part of #45

Add ScalaCli builder type and integrate it with the common ProjectTemplate generation that includes: * main/endpoints/test sources * scalafmt * group id specific README.md file Part of #45

Scala Cli allows to provide project parameters like name, version etc. either as a command line parameter or as a part of 'sc' or 'scala' files. Introduce 'build.sc' file that contains: * all project related information * libraries import necessary to compile/run/package etc. generated project in question The 'builder.sc' file is generated only when Scala-Cli builder is selected. Part of #45

Scala-cli allows to provide test dependencies inside spec and '.sc' files. Introduce 'test.sc' file that is located under 'src/test/scala/' directory to contain all test related dependencies in a single file. Placing it in 'src/test/scals' prevents test dependencies from being incorporated into production package. Part of #45

Extend the existing integration tests to cover also `scala-cli` builde configuratiion. Part of #45

Add ScalaCli builder type and integrate it with the common ProjectTemplate generation that includes: * main/endpoints/test sources * scalafmt * README.md file Part of #45

Scala Cli allows to provide project parameters like name, version etc. either as a command line parameter or as a part of 'sc' or 'scala' files. Introduce 'build.sc' file that contains: * all project related information * libraries import necessary to compile/run/package etc. generated project in question The 'builder.sc' file is generated only when Scala-Cli builder is selected. Part of #45

Scala-cli allows to provide test dependencies inside spec and '.sc' files. Introduce 'test.sc' file that is located under 'src/test/scala/' directory to contain all test related dependencies in a single file. Placing it in 'src/test/scals' prevents test dependencies from being incorporated into production package. Part of #45

Extend the existing integration tests to cover also `scala-cli` builde configuratiion. Part of #45

Extend the existing integration tests to cover also `scala-cli` builder configuratiion. Part of #45

Extend the existing integration tests to cover also `scala-cli` builder configuratiion. Note that the existing `adopt-tapir-ci.yml` was extended with `VirtusLab/scala-cli-setup@v0.1` action. Part of #45

Extend the existing integration tests to cover also `scala-cli` builder configuratiion. Notes: * the existing `adopt-tapir-ci.yml` was extended with `VirtusLab/scala-cli-setup@v0.1` action. * cli setup used JDK 17 (temurin distro) therefore existing JDK setup modified to setup this version Part of #45

Changes: * add builder parameter with default value Sbt to both request and model objects * identify Sbt related classes/methods/members and add 'sbt' infix to them Part of #45

Add ScalaCli builder type and integrate it with the common ProjectTemplate generation that includes: * main/endpoints/test sources * scalafmt * README.md file Part of #45

Scala Cli allows to provide project parameters like name, version etc. either as a command line parameter or as a part of 'sc' or 'scala' files. Introduce 'build.sc' file that contains: * all project related information * libraries import necessary to compile/run/package etc. generated project in question The 'builder.sc' file is generated only when Scala-Cli builder is selected. Part of #45

Scala-cli allows to provide test dependencies inside spec and '.sc' files. Introduce 'test.sc' file that is located under 'src/test/scala/' directory to contain all test related dependencies in a single file. Placing it in 'src/test/scals' prevents test dependencies from being incorporated into production package. Part of #45

Extend the existing integration tests to cover also `scala-cli` builder configuratiion. Notes: * the existing `adopt-tapir-ci.yml` was extended with `VirtusLab/scala-cli-setup@v0.1` action. Part of #45

Extend the existing integration tests to cover also `scala-cli` builder configuratiion. Notes: * the existing `adopt-tapir-ci.yml` was extended with `VirtusLab/scala-cli-setup@v0.1` action. * JVM setup was removed as JVM is being set by installation of coursier (for scala-cli) Part of #45

Extend the existing integration tests to cover also `scala-cli` builder configuratiion. Notes: * the existing `adopt-tapir-ci.yml` was extended with `VirtusLab/scala-cli-setup@v0.1` action. * JVM setup was removed as JVM is being set by installation of coursier (for scala-cli) * 'waitForPortTimeout' was extended to 120s as the initial `scala-cli` call requires extra time to warm-up Part of #45

Extend the existing integration tests to cover also `scala-cli` builder configuratiion. Notes: * the existing `adopt-tapir-ci.yml` was extended with `VirtusLab/scala-cli-setup@v0.1` action. * JVM setup was removed as JVM is being set by installation of coursier (for scala-cli) * 'scala-cli' cannot be chained to call compile, test and run in a signle line therefore compile and test is called when 'ScalaCliService' is created and then run is spawned. It affects the resource creation therefore it is a subject of timeout (by default 30s) therefore new 'waitForScalaCliCompileAndUnitTest' (45s) was introduced to add it a bit more space as CI was timing out on it. Part of #45

Add ScalaCli builder type and integrate it with the common ProjectTemplate generation that includes: * main/endpoints/test sources * scalafmt * README.md file Part of #45

Scala Cli allows to provide project parameters like name, version etc. either as a command line parameter or as a part of 'sc' or 'scala' files. Introduce 'build.sc' file that contains: * all project related information * libraries import necessary to compile/run/package etc. generated project in question The 'builder.sc' file is generated only when Scala-Cli builder is selected. Part of #45

Scala-cli allows to provide test dependencies inside spec and '.sc' files. Introduce 'test.sc' file that is located under 'src/test/scala/' directory to contain all test related dependencies in a single file. Placing it in 'src/test/scals' prevents test dependencies from being incorporated into production package. Part of #45

Extend the existing integration tests to cover also `scala-cli` builder configuratiion. Notes: * the existing `adopt-tapir-ci.yml` was extended with `VirtusLab/scala-cli-setup@v0.1` and 'coursier/cache-action@v6.3' actions * JVM setup was removed as JVM is being set by installation of coursier (for scala-cli) * 'scala-cli' cannot be chained to call compile, test and run in a signle line therefore compile and test is called when 'ScalaCliService' is created and then run is spawned. It affects the resource creation therefore it is a subject of timeout (by default 30s) therefore new 'waitForScalaCliCompileAndUnitTest' (45s) was introduced to add a bit more space to it so that CI will not time out * 'waitForPort' failure was improved to contain full stack exception stack trace so that it is easier to debug what failed Part of #45

Changes: * add builder parameter with default value Sbt to both request and model objects * identify Sbt related classes/methods/members and add 'sbt' infix to them Part of #45

Extend the existing integration tests to cover also `scala-cli` builder configuratiion. Notes: * the existing `adopt-tapir-ci.yml` was extended with `VirtusLab/scala-cli-setup@v0.1` and 'coursier/cache-action@v6.3' actions * JVM setup was removed as JVM is being set by installation of coursier (for scala-cli) * 'scala-cli' cannot be chained to call compile, test and run in a signle line therefore compile and test is called when 'ScalaCliService' is created and then run is spawned. It affects the resource creation therefore it is a subject of timeout (by default 30s) therefore new 'waitForScalaCliCompileAndUnitTest' (45s) was introduced to add a bit more space to it so that CI will not time out * 'waitForPort' failure was improved to contain full stack exception stack trace so that it is easier to debug what failed Part of #45

Extend the existing integration tests to cover also `scala-cli` builder configuratiion. Notes: * the existing `adopt-tapir-ci.yml` was extended with `VirtusLab/scala-cli-setup@v0.1` and 'coursier/cache-action@v6.3' actions * JVM setup was removed as JVM is being set by installation of coursier (for scala-cli) * 'scala-cli' cannot be chained to call compile, test and run in a signle line therefore compile and test is called when 'ScalaCliService' is created and then run is spawned. It affects the resource creation therefore it is a subject of timeout (by default 30s) therefore new 'waitForScalaCliCompileAndUnitTest' (45s) was introduced to add a bit more space to it so that CI will not time out * the same timeout (minus 1s) is used in order to wait for scala-cli compilation server * 'waitForPort' failure was improved to contain full stack exception stack trace so that it is easier to debug what failed Part of #45