Skip to content

Comments

chore: Use standard sbt#875

Draft
jorgeazevedo wants to merge 1 commit intomainfrom
ja-use-standard-sbt
Draft

chore: Use standard sbt#875
jorgeazevedo wants to merge 1 commit intomainfrom
ja-use-standard-sbt

Conversation

@jorgeazevedo
Copy link
Contributor

What does this change?

Replace the custom ./sbt wrapper script (which bundled sbt-launch.jar) with the standard sbt command, moving JVM options to .jvmopts and the local dev config to build.sbt.

How has this change been tested?

Have we considered potential risks?

@jorgeazevedo jorgeazevedo added the maintenance Departmental tracking: maintenance work, not a fix or a feature label Feb 24, 2026
@github-actions
Copy link
Contributor

github-actions bot commented Feb 24, 2026

@jorgeazevedo jorgeazevedo force-pushed the ja-use-standard-sbt branch 3 times, most recently from 5378656 to 6328e32 Compare February 24, 2026 10:51
Remove the custom ./sbt script that bundled sbt-launch.jar and replace
it with the standard sbt command. JVM memory options are now configured
in .jvmopts, and the local dev config file is set via build.sbt
(run / javaOptions).

This aligns with modern sbt best practices where sbt is installed on the
machine and fetches the right version from project/build.properties.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

maintenance Departmental tracking: maintenance work, not a fix or a feature

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant