-
Notifications
You must be signed in to change notification settings - Fork 24.9k
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
Changes to keep Checkstyle happy after reformatting #76464
Changes to keep Checkstyle happy after reformatting #76464
Conversation
Pinging @elastic/es-delivery (Team:Delivery) |
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.
LGTM
@@ -169,6 +169,12 @@ dependencies { | |||
String grammarPath = 'src/main/antlr' | |||
String outputPath = 'src/main/java/org/elasticsearch/painless/antlr' | |||
|
|||
spotless { | |||
java { | |||
targetExclude "${outputPath}/*.java" |
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.
Ug, we really should be putting generated source elsewhere instead of mixing it with the main sourceset. Let's add a TODO
here.
I just remembered, should we follow up and add this to |
I see why we might do that, but I've edited config files as well, and I'd still want those changes to show up in |
@elasticmachine update branch |
* Reformatting to keep Checkstyle after formatting * Configure spotless everywhere, and disable the tasks if necessary * Add XContentBuilder helpers, fix test
Make a number of tweaks to the source so that in the future, after a complete reformat with Spotless, Checkstyle is still happy with the code.
Also:
MachineLearningGetResultsIT
since it was unreadable.XContentBuilder
that will format better