eugene yokota

> However, the first invocation still doesn't print the "success" output. ok. Let me reopen this issue.

To avoid classloading scala-library and scala-compiler, sbt launcher creates directories for: - boot Scala version (the Scala version used by metabuild) - boot JARs (the rest of sbt main JARs)...

Zinc is cross published to Scala 2.13 for 1.x branch. I guess the complication is that there are modules in sbt like library management that use scala-xml but doesn't depend...

If you want Java sources to participate in the incremental compilation, then you might need to use Zinc to compile Java so we can analyze them. I didn't read the...

> Is there a way to use zinc only for scala incremental compilation? Zinc can compile against JAR files that was compiled from pure Java, so you would probably have...

> Can you at least give some pointers on where to look for implicit inputs? Programs are sequence of p⇒q logic, where the precondition p needs to hold for the...

I've set up release automation, and published: - https://github.com/sbt/sbt-jupiter-interface/releases/tag/v0.11.3 - https://github.com/sbt/sbt-jupiter-interface/releases/tag/v0.11.4 (JUnit 5.9.3) and sent https://github.com/sbt/sbt-jupiter-interface/pull/87 for `@Suite` support. I could not reproduce #41 though.

@vasilmkd I've split the above comment into a new issue - https://github.com/sbt/sbt-jupiter-interface/issues/89

When we bump the AnalysisCallback, we probably want to send PRs to Scala 2.13 and Scala 3 so the Scala teams don't have to figure out what to change.

This is probably a good idea, but we need to remove the usage side first before breaking sbt?