Code base doesn't comply with JUnit's own coding style
See original GitHub issueI’d like to suggest to reformat all code under org.junit.*
once to meet the defined formatting guidelines.
At the moment not all the files are formatted accordingly to that standard. This causes problems for contributors - especially in pull request. If you format the code you get a lot of extraneous diffs - just because of the reformatting - in addition to your actual changes.
I think it’s not too late to do this formatting. Regarding existing PRs that tried to preserve the outdated styling: They would get extraneous diffs then of course, but if they apply the new format as well everything would be fine again. In addition, I think many of PRs are dead anyway, since many of them haven’t seen any updates for months or even years.
As a result, contributing to JUnit 4 and reviewing the changes by the core team should become easier in the future.
Issue Analytics
- State:
- Created 7 years ago
- Comments:7 (7 by maintainers)
Top GitHub Comments
A non-Eclipse solution could be to use google-java-format. There’s also a googleformatter-maven-plugin.
I added a comment on PR #1379; seems four space indentation should be possible after all 😃.