-
Notifications
You must be signed in to change notification settings - Fork 28.9k
[WIP][SPARK-30194][BUILD][test-maven] Re-enable checkstyle for Java #26820
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
Conversation
|
Sure, but, heh does it actually pass right now? |
|
Yes. |
|
Oh, let me check the build-error part once more. |
|
Test build #115047 has finished for PR 26820 at commit
|
|
Retest this please. |
|
Btw, I'm feeling that it might be too strict to throw error on unused imports; as it could happen when multiple PRs modify the same file. Scala checkstyle doesn't throw error on unused imports, right? |
|
Ya. That's a good point. Let me think about that, too. |
|
We enabled checkstyle in PR builder via #21399. So does this PR only apply when PR has the title |
| <version>3.1.0</version> | ||
| <configuration> | ||
| <failOnViolation>false</failOnViolation> | ||
| <failOnViolation>true</failOnViolation> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
|
Test build #115050 has finished for PR 26820 at commit
|
|
Hi, All. Thank you for review. We had better remove the |
What changes were proposed in this pull request?
This PR aims to prevent Java checkstyle violation.
Why are the changes needed?
Historically, we disabled this because there was no way to check this in PR Builder (9b98aef).
However, now we have
GitHub Actionwhich do this every PR.Does this PR introduce any user-facing change?
No.
How was this patch tested?
Manually.