eugene yokota comments

Results 742 comments of


                                            eugene yokota

"value getOffsetStatic is not a member of object scala.runtime.LazyVals" while testing Java-only library with ScalaTest + Scala 3.4.1

ok, so to clarify the goal here, you want to: 1. make a Java-only library, and thus set `autoScalaLibrary := false` on the subproject 2. but use the latest Scala...

Allow the sbt launcher to be called programmatcially without running into an `exit` call

Probably coming from https://github.com/sbt/launcher/blob/1.x/launcher-implementation/src/main/scala/xsbt/boot/Boot.scala. Would a system property like `sbt.boot.exit=false` work?

Allow the sbt launcher to be called programmatcially without running into an `exit` call

I don't know if the original scope of sbt launcher was to be a generic launcher, but given that almost no one else but sbt uses it I'd suggest looking...

Allow the sbt launcher to be called programmatcially without running into an `exit` call

https://github.com/sbt/launcher hosts launcher-interface and launcher. launcher-interface is the Java interface that exposes an API to the application to be launched, whereas `launcher` is an über JAR of a generic launcher...

Allow the sbt launcher to be called programmatcially without running into an `exit` call

> Anyway, what I'm looking for is a way to programmatically bootstrap the SBT version... All in all, what's your recommendation how to achieve that currently? To some extent that's...

Allow the sbt launcher to be called programmatcially without running into an `exit` call

In addition to `project/build.properties`, people can pass in sys props directly from the command line, or use `.sbtopts` file interpreted in https://github.com/sbt/sbt/blob/1.10.x/sbt. It might be relatively easy to start "some...

[1.3.x] object X is not a member of package Y

@meier-christoph Thanks for the report. Could you provide reproduction steps so we can reproduce your problem on _our computers_? You mentioned classloader, but I am wonder if this is actually...

[1.3.x] object X is not a member of package Y

Yea. To clarify, I'm not saying that we won't accept this bug report without repro steps. But without reproduction, it's hard to characterize this problem at this point. Note for...

[1.3.x] object X is not a member of package Y

We can rule out Coursier if the problem persists with ```scala ThisBuild / useCoursier := false ```

[1.3.x] object X is not a member of package Y

Thanks for the public repro.