| 19 Dec 2023 |
 j_mie6 | Looks like I needed to explicitly add //> using testFramework org.scalatest.tools.Framework | 14:22:37 |
| j_mie6 | But I'm not sure why... Perhaps because of the extra scalatestplus dependency? | 14:23:22 |
| j_mie6 | 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 |
|  steadhaven changed their display name from marouan28 to steadhaven. | 14:38:12 |
| 22 Dec 2023 |
|  mglvl changed their display name from miguelvilag to mglvl. | 16:28:53 |
 jd557 | 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 | 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 |
 Tomasz Godzik | you should be able to turn off the warning, but this also seems worth to mention in an issue | 17:30:31 |
| Tomasz Godzik | 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 | 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 | Full command: | 17:36:50 |
| earldouglas | * 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 | * 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 |
| earldouglas | * 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 \
-P:continuations:enable \
myscript.sc
| 17:38:29 |
| earldouglas | * 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:38:36 |
| earldouglas | For reference, how to do this in sbt: https://stackoverflow.com/questions/2683195/how-do-i-enable-continuations-in-scala/2683215#2683215 | 17:41:45 |
 armanbilge | seems like it should just work | 17:43:54 |
| armanbilge | https://scala-cli.virtuslab.org/docs/reference/cli-options/ | 17:43:55 |
| earldouglas | From --scalac-verbose, it looks like the plugin is being loaded correctly: loaded plugin continuations. Makes me wonder if the -P: argument is not being propagated to scalac. | 17:46:08 |
 sake92 | Try --scala-option -P... | 17:46:56 |
 sethtisue | https://github.com/VirtusLab/scala-cli/issues/2621 might have relevant info? seems like --server=false might be worth trying? | 17:51:59 |
| sethtisue | * https://github.com/VirtusLab/scala-cli/issues/2621 might have relevant info? seems like --server=false might be worth trying? | 17:52:06 |
| sethtisue | * https://github.com/VirtusLab/scala-cli/issues/2621 might have relevant info? seems like --server=false might be worth trying? | 17:52:08 |
| sethtisue | * https://github.com/VirtusLab/scala-cli/issues/2621 might have relevant info? seems like --server=false might be worth trying? | 17:52:25 |
| armanbilge | does it work if you do //> using directives instead? | 17:55:45 |
| sethtisue | I'm able to reproduce the problem, and running scala-cli with -v -v shows that the -P... argument simply isn't passed on | 18:02:10 |
| earldouglas | That works! | 18:02:54 |
| earldouglas | Confirmed; I can fix it by either moving all options under //> using, or by moving just the -P: option under //> using. | 18:04:13 |
| sethtisue | if you have a spare minute, please file a bug report. I don't see an existing one | 18:04:36 |
| earldouglas | Sure thing; will do later today. | 18:05:06 |
