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

Discrepancy between this plugin and running google-java-format jar directly #184

Open
jduan-highnote opened this issue Oct 30, 2023 · 3 comments

Comments

@jduan-highnote
Copy link

We are using the latest version (2.21.1) of this plugin. On top of that, we also have a git pre-commit hook that uses the google-java-format jar directly on changed files. We use 1.17.0 of the jar, which matches the version used in the pom.xml of this plugin.

However, they produce different results. For example, we have one Java file which has very long literal strings.

  • this plugin doesn't break up those long lines
  • running the jar directly does break them up into shorter lines

How do we make them produce the same result? Thanks!

@fxfh0504
Copy link

I have the same question.

@scch-michael-pfeiffer
Copy link

Could be caused because this Maven plugin does implicitly use this flag: --skip-reflowing-long-strings

@jduan-highnote
Copy link
Author

Thanks for filing #197. I'll follow it.

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

No branches or pull requests

3 participants