| 19 Dec 2023 |
 jmie6 | The test command just seems to be compiling the test project (properly, I'll add), but then doesn't decide to execute anything | 12:57:06 |
| jmie6 | I'll... Try... Not sure how to minimise this exactly | 13:35:30 |
| jmie6 | Also, when setting the packageType to native in a build where using platform jvm native still requires passing --native on the command line (it tries to package with JVM otherwise and fails to find native); I assume this is unintentional and deserves an issue? | 13:37:05 |
| jmie6 | So it looks like the debug console for the metals green button shows the output of the tests just fine, but the test results panel does not | 13:43:34 |
| jmie6 | If I run scala-cli test . it compiles but doesn't run anything | 13:49:58 |
| jmie6 | Which is why it's weird, the green button is doing more | 13:50:17 |
| jmie6 | -v -v -v didn't show anything interesting | 13:50:29 |
| jmie6 | Scala test anyflatspec is what the classes are using | 13:51:01 |
| jmie6 | Is there anything obvious I would be missing? I have src/main/scala/pkg and src/test/scala/pkg folders alongside my project.scala | 13:53:31 |
| jmie6 | Project scala specifies the testdep on scalatest and also scalacheck (via scalatestplus) | 13:54:05 |
| jmie6 | Yeah, I've definitely had it work before | 13:58:52 |
| jmie6 | Just... Not here | 13:58:55 |
| jmie6 | This is a project I just ported over from sbt | 13:59:11 |
| jmie6 | Nothing, just compiling, compiled, then command ends | 13:59:25 |
| jmie6 | I can give the -v -v -v log if that helps | 14:00:59 |
| jmie6 | I can put it in an issue | 14:01:08 |
| jmie6 | Thanks | 14:01:29 |
| jmie6 | Looks like I needed to explicitly add //> using testFramework org.scalatest.tools.Framework | 14:22:37 |
| jmie6 | But I'm not sure why... Perhaps because of the extra scalatestplus dependency? | 14:23:22 |
| jmie6 | With --require-tests it was failing because it couldn't find any tests... So perhaps it was using the wrong framework, though the -v -v -v didn't specify which framework it had found | 14:25:51 |
|  Zone of proximal development changed their display name from marouan28 to steadhaven. | 14:38:12 |
| 22 Dec 2023 |
|  miguel changed their display name from miguelvilag to mglvl. | 16:28:53 |
 JD557#8432 | I'm getting the following warning on Scala-CLI 1.1.0
[warn] Using directives detected in multiple files:
- publish-conf.scala:1:1-14:54
It is recommended to keep them centralized in the D:\Projects\spaeti\project.scala file.
Is this something new? I don't think I was getting this warning before (I'm on a different machine, though) | 17:51:42 |
| JD557#8432 | I find this a bit surprising, since the project.scala/publish-conf.scala split seems to be the recommended way to do things :/ | 17:52:18 |
| 27 Dec 2023 |
 tgodzik#4885 | you should be able to turn off the warning, but this also seems worth to mention in an issue | 17:30:31 |
| tgodzik#4885 | there are a couple of options, they ar ementioned here https://scala-cli.virtuslab.org/docs/guides/power/repositories#repository-authentication | 17:34:21 |
| 29 Dec 2023 |
 earldouglas#9613 | Anyone familiar with passing options to scalac? I have a plugin argument (-P;continuations:enable) that seems to be ignored (this code must be compiled with the Scala continuations plugin enabled). Same behavior whether I include or omit that -P argument. | 17:35:05 |
| earldouglas#9613 | Full command: | 17:36:50 |
| earldouglas#9613 | * Full command:
scala-cli --scala 2.12.2 --compiler-plugin org.scala-lang.plugins:::scala-continuations-plugin:1.0.3 --dependency org.scala-lang.plugins::scala-continuations-library:1.0.3 myscript.sc
| 17:37:21 |
| earldouglas#9613 | * Full command:
scala-cli \
--scala 2.12.2 \
--compiler-plugin org.scala-lang.plugins:::scala-continuations-plugin:1.0.3 \
--dependency org.scala-lang.plugins::scala-continuations-library:1.0.3 \
myscript.sc
| 17:37:48 |
