Sender | Message | Time |
---|---|---|
21 May 2024 | ||
* i.e., how do I tell testOnly to produce some sort of error if the indicated class does not exist? | 11:17:38 | |
I could also go for an autocomplete that does an outline parse to find test class names (when not already compiled). | 11:26:52 | |
18:26:58 | ||
20:49:14 | ||
21:37:28 | ||
22 May 2024 | ||
04:21:47 | ||
05:58:54 | ||
no build target found for scala files, can anyone help? | 05:58:55 | |
05:58:55 | ||
perhaps we can help, but we’ll need more information about what you tried and precisely what error message (or other unexpected behavior) you got | 11:30:34 | |
12:30:46 | ||
12:30:47 | ||
Hello everyone, I have been getting this kind of messages all week [error] SERVER ERROR: Gateway Time-out url=https://repo.typesafe.com/typesafe/ivy-releases/io.ebean/ebean-agent/11.5.1/jars/ebean-agent.jar [error] SERVER ERROR: Bad Gateway url=https://repo.scala-sbt.org/scalasbt/sbt-plugin-releases/org.scala-sbt/util-position_2.12/1.1.3/ivys/ivy.xml [error] SERVER ERROR: Bad Gateway url=https://repo.typesafe.com/typesafe/ivy-releases/org.scala-sbt/util-position_2.12/1.1.3/jars/util-position_2.12.jar [error] SERVER ERROR: Bad Gateway url=https://repo.scala-sbt.org/scalasbt/sbt-plugin-releases/org.scala-sbt/util-position_2.12/1.1.3/jars/util-position_2.12.jar sometimes it works but takes a lot of time (~30 min) to resolve those downloads | 12:30:47 | |
https://status.jfrog.io/ announced a very small outage on the 19th but it has been happening to me all day these week | 12:33:01 | |
Seeing a similar issue on my end beginning mid-morning UTC with a mix of 502, 504, and connection reset errors when downloading artifacts for publicly available sbt plugins. The scala Artifactory page https://scala.jfrog.io/ui/packages is also brutally slow to load up today. | 12:37:26 | |
12:37:26 | ||
also, when pasting one of those urls on the browser i get | 12:39:38 | |
12:39:39 | ||
ticket is https://github.com/sbt/sbt/issues/7566 , please record your experiences there. I think Eugene was somewhat dismissive of the original report since the delay was measured in seconds not minutes and there weren't error codes. but it seems like the issue has worsened | 12:45:38 | |
Thank you Seth! | 12:46:02 | |
(but do note also what I wrote about using current sbt with current plugins as a likely workaround) | 12:46:08 | |
* (but do note also what I wrote on-ticket about using current sbt with current plugins as a likely workaround) | 12:46:58 | |
What is the best workflow to work with multiple sbt projects simultaneously that need to be ran on different JDK versions? I am looking for something cross-platform and automatic, so that I would not need to figure out which JDK version to switch to on shell/project/IDE combo manually. Looking at sbt launcher I saw this bit in Windows launcher - https://github.com/sbt/sbt/blob/b27c7253b19fb6008566796c914063cec22c18ce/launcher-package/src/universal/bin/sbt.bat#L83-L88, basically having JAVA_HOMES env variable and .java-version file in project the launcher would run sbt with correct JDK. I have tried it and I have not managed to get it to work. I am thinking about creating a PR to revive this functionality and make it available for all platforms if there is no better alternative already available. | 13:32:19 | |
A project I work on has this exact requirement, achieved by using a special plugin: https://github.com/sourcegraph/scip-java/blob/main/project/JavaToolchainPlugin.scala I've found that this conflicts with something that Metals and sbt BSP do with each other, but apart from that it seems to mostly work | 13:38:03 | |
Neat! Though you mentioning that Metals and sbt BSP has issues with this approach means it probably won't work with my primary workflow - sbt BSP with IntelliJ IDEA. | 13:40:19 | |
sbt launcher supporting this is probably the best place to make sure it works with most workflows. | 13:40:54 | |
yeah agree, supporting toolchains would be great that said, do give this approach a go (you can just copy the file to your project) | 13:43:12 | |
Ah, your plugin is even fancier than what I would require - I am fine with whole sbt project being booted with certain JVM, I just might have multiple projects open that run on different JDKs. Where your plugin is about modules within sbt project being compiled on different JVMs. Pretty funky! | 13:46:59 | |
can just do coursier launch --jvm 11 sbt to launch SBT 🙂 | 13:48:06 | |
I would like to standardize a way to avoid the --jvm 11 part and somehow set the project's JDK implicitly. Like that .java-version file that the Windows sbt launcher uses. | 13:50:15 |