 | sbt | 2088 Members |
| Scala Build Tool | 5 Servers |
| sbt | 2088 Members |
| Scala Build Tool | 5 Servers |
| Sender | Message | Time |
|---|---|---|
| 16 May 2024 | ||
 mikimm16 | | 10:51:36 |
| mikimm16 | There are more errors as the ones I provided, but all seem to be corelated to semanticdb-scalac_2.13.12. Do you know how can I resolve this problem and build the project? | 10:51:48 |
 bjornregnell changed their profile picture. | 11:22:04 | |
| bjornregnell | https://github.com/sbt/sbt/issues/7560 | 12:10:26 |
| bjornregnell | Is this sbt specific? I think so as it works fine with scala-cli 1.3.1 with Scala 3.4.1.... | 12:11:34 |
| bjornregnell |  Download 331195693-fd67dbee-c3d7-41dc-b90d-a3831ef83d5b.png | 12:11:43 |
| bjornregnell | * I was just hit by this bug when bumping to Scala 3.4.1: https://github.com/sbt/sbt/issues/7560 | 12:17:54 |
 fel_her | Is there an easy way to run my to run my tests against different versions of a library I depend on to see with which versions everything works? | 14:58:12 |
| fel_her | * Is there an easy way to run my tests against different versions of a library I depend on to see with which versions everything works? | 15:08:22 |
 som-snytt | I commented on the ticket that https://github.com/scala/scala3/pull/20409 might have related information. (I don't know anything about it, but it says sbt and module-info.) | 16:02:46 |
 adpi2 | In build.sbt there is a Global / semanticdbVersion := "4.5.13". This is incorrect. You need to bump the version to 4.9.4. And then if you can open a PR that would be great. Or I'll do it next week. | 16:07:24 |
| adpi2 | * In build.sbt line 50 there is a Global / semanticdbVersion := "4.5.13". This is incorrect. You need to bump the version to 4.9.4. And then if you can open a PR that would be great. Or I'll do it next week. | 16:07:46 |
| bjornregnell | Aha!! See my question to you on reproduction here https://github.com/sbt/sbt/issues/7560 | 16:19:47 |
 sethtisue | dead easy, no — not that I can think of, anyway easy-ish, yes, I think so; write a custom command that changes the version, runs the tests, changes the version again, runs the tests again, and so on it's up to you whether it's easier to write that command using the sbt APIs, or whether it's easier to handwrite or code-generate a shell script to drive sbt through these steps. or to do it in a GitHub Actions (or other CI system) matrix | 16:21:04 |
| sethtisue | * dead easy, no — not that I can think of, anyway easy-ish, yes, I think so; for example, you could write a custom command that changes the version, runs the tests, changes the version again, runs the tests again, and so on it's up to you whether it's easier to write that command using the sbt APIs, or whether it's easier to handwrite or code-generate a shell script to drive sbt through these steps. or to do it in a GitHub Actions (or other CI system) matrix | 16:21:29 |
| sethtisue | offhand I think I'd lean towards a CI matrix? but not really sure, ymmv | 16:22:01 |
| bjornregnell | I'd use os-lib in a scala-cli script. | 16:22:05 |
| bjornregnell | * I'd use os-lib in a scala-cli script. https://github.com/com-lihaoyi/os-lib See os.proc | 16:22:43 |
| fel_her | Redacted or Malformed Event | 16:23:04 |
| bjornregnell | * I'd use os-lib in a scala-cli script. https://github.com/com-lihaoyi/os-lib See os.proc and call the native sbt --client from an os.proc | 16:23:26 |
| bjornregnell | * I'd use os-lib in a scala-cli script. https://github.com/com-lihaoyi/os-lib See os.proc and call the native sbt --client from an os.procos lib is available by a simple in scala-cli | 16:24:02 |
| fel_her | sethtisue bjornregnell Thank you both. Yeah, I might just script it. Is this something that project-matrix can do? I think it can do different scala-versions and platforms and has axis you can configure. But I haven't completely understood it yet. | 16:24:29 |
| fel_her | * sethtisue bjornregnell Thank you both. Yeah, I might just script it. Is this (different dependencies) something that project-matrix can do? I think it can do different scala-versions and platforms and has axis you can configure. But I haven't completely understood it yet. | 16:24:39 |
| bjornregnell | Probably easier just to programatically replace some setting in build.sbt and run again... | 16:25:11 |
| bjornregnell | But you could probably write an sbt plugin; if you put scala code in the project folder it is available in your build | 16:25:49 |
| bjornregnell | * But you could probably instead write an sbt plugin; if you put scala code in the project folder it is available in your build | 16:26:00 |
| bjornregnell | https://www.scala-sbt.org/1.x/docs/Plugins.html | 16:26:20 |
| sethtisue | how big is n here? n = 2? n = 10? might change how I feel about it | 16:26:36 |
| fel_her | I think 2 scala versions and 5 dependency versions | 16:27:19 |
| sethtisue | do you need to publish separately for different versions of the library? or just run the tests? | 16:27:35 |