Support overriding the formatter Java home#271
Merged
Conversation
b137422 to
ccaaaff
Compare
Closed
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
1 participant
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.
Adds explicit Java home overrides for the forked
google-java-formatJVM.The plugin currently falls back to the same Java installation used by the sbt process via
java.home. This works well by default, but on CI servers or developer machines it can be useful to run the formatter with a different JDK without changing the JDK that sbt itself runs on.This change adds two override mechanisms:
sbt-javafmt.java.homeSBT_JAVAFMT_JAVA_HOMEResolution order is now:
sbt-javafmt.java.homeSBT_JAVAFMT_JAVA_HOMEjava.homeSo users can now do either of these:
The plugin still defaults to sbt's own
java.homewhen neither override is set.