Repository navigation
Conversation
…-multi-jvm-config Support multi-jvm source directories in sbt
…nsole Add regression test for the Ammonite console on JDK > 8
…ion-env-vars Add end-to-end BSP test for debug session environment variables
…king-dir Run BSP targets in the project working directory
…-classic-1.5.34 build(deps): Update logback-classic from 1.5.33 to 1.5.34
…ss-2.3.13 build(deps): Update shapeless from 2.3.4 to 2.3.13
chore: Update utest to 0.9.5
…lude-dependencies Combine --cascade with --include-dependencies in test and clean
The sbt-bloop plugin exports the sbt meta-build (the build definition under project/) on every load so Metals can compile it. This made sbt startup slower and noisier than without the plugin. - Skip the on-load export when a fingerprint of the files under project/ is unchanged. The fingerprint is stamped in .bloop whenever bloopInstall exports the meta-build, so startup is fast and silent once the build definition is stable, while edits/additions/deletions still regenerate. - Log the automatic export at debug level; a manual bloopInstall still reports as before. - Add a bloopExportMetaBuild opt-out via the BLOOP_EXPORT_META_BUILD environment variable / bloop.export-meta-build system property (global, covers nested meta-builds) or the per-layer setting. Adds scripted tests for change detection (edit/add/delete) and the opt-out across nested meta-build layers.
A relative single-segment unmanaged resource (e.g. file("file1.yml"))
has a null parent, which ConfigUtil.pathsOutsideRoots dereferenced via
toAbsolutePath, crashing bloopInstall/bloopGenerate. Route both callers
through one helper that normalizes the roots and the candidate paths to
absolute before delegating, so the parent is never null and in-root
resources aren't misclassified when roots are relative. Adds a scripted
regression test for a subproject exporting a resource outside its root.
…-command Print the about banner for `bloop --version` and `bloop version`
…esources-npe Fix NullPointerException for relative paths in sbt unmanagedResources
Prints a per-module compile summary after the compile run completes. Opt-in via --summary so it does not affect interactive or IDE use. The summary shows: - Each project's compile time (slowest first), annotated (failed) or (cancelled) when the compile did not succeed - Projects blocked on a failed upstream (e.g. "b - blocked on a"), sourced from the dag closure so repeated failures don't drop them - Total module compile time (sum of per-module times) - Wall-clock duration (covers the full run, including any --incremental false clean step)
…ash-stacktrace Report a crash from the compiler instead of hanging the compilation
Clean deleted the class directories but kept the persisted Zinc analysis, so after a server restart the stale analysis was reloaded and the next compile ran incrementally against it. Converting a package into a top-level object of the same name then kept reporting "<object> is already defined as package <package>" until .bloop was removed by hand. Delete the analysis file for every cleaned target and drop the in-memory last successful result so clean resets incremental state the same way removing .bloop does.
…2.12 build(deps): Update sbt, scripted-plugin, test-agent from 1.12.11 to 1.12.12
…core-7.3.9 build(deps): Update scalaz-core from 7.3.8 to 7.3.9
….3.3 build(deps): Update munit from 1.3.1 to 1.3.3
…ore-2.26.0 build(deps): Update log4j-core from 2.23.1 to 2.26.0
…lafix-0.14.7 build(deps): Update sbt-scalafix from 0.14.6 to 0.14.7
build(deps): Update jna from 5.19.0 to 5.19.1
…-summary Add --summary flag to bloop compile
…-analysis Fully reset incremental state on clean
chore: Update sbt 2 to final release
…a-build-export Change-detect and quiet the automatic sbt meta-build export
…ug-flag Add --jvm-debug flag to run and test for attaching a debugger
…rogrammatic-resolution # Conflicts: # frontend/src/main/scala/bloop/engine/Interpreter.scala
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Stacked on
fix/1226-ammonite-console(upstream PR scalacenter#2941); review shows just the single follow-up commit.bloop consoleshelled out to acoursier/cslauncher on the client's PATH and requestedammonite_<exactScalaVersion>:latest.release. So it failed with a bare "command not found" when no launcher was present, and with a raw coursier stack trace when Ammonite wasn't published for the project's exact Scala version.This resolves the REPL artifacts with bloop's existing coursier API (
DependencyResolution) and emits a plainjava -cp ... <main>command instead:javais needed);Applies to both the Ammonite and Scala REPLs.
ConsoleSpecnow launches the generated command end-to-end and asserts the project's classes are visible in the REPL.