Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fork on java 9+ #150

Merged
merged 2 commits into from
Mar 29, 2022
Merged

Fork on java 9+ #150

merged 2 commits into from
Mar 29, 2022

Conversation

danielnorberg
Copy link
Contributor

@klaraward
Copy link
Contributor

Yeah, I agree the warnings are not nice. It's a balance between warnings and the small extra overhead of forking. My original thought was to avoid forking, but lets go with the more reasonable avoiding unnecessary warnings :)

@@ -99,7 +99,7 @@ For example, you may prefer that the `check` goal is performed in an earlier pha

`style` sets the formatter style to be `google` or `aosp`. By default this is `google`. Projects using Android conventions may prefer `aosp`.

`forkMode` lets you specify whether to run google-java-format in a fork or in-process. Also adds JVM arguments when needed. Value `default` will fork when JDK 16+ is detected, `never` runs in-process, regardless of JDK version and `always` will always fork.
`forkMode` lets you specify whether to run google-java-format in a fork or in-process. Also adds JVM arguments to expose JDK internal javac APIs. Value `default` (which is the default) will fork (to avoid warnings for JDK9+ and to be able to run at all for JDK16+), `never` runs in-process, regardless of JDK version and `always` will always fork.
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⭐️

@danielnorberg danielnorberg marked this pull request as ready for review March 29, 2022 11:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants