Use upstream Spotless configuration #188
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As of jenkinsci/plugin-pom#733 the upstream plugin parent POM provides a standard Spotless configuration that Jenkins plugins can opt into by adding a .mvn_exec_spotless file. This PR removes the custom Spotless configuration in this repository in favor of the upstream one and reformats the entire repository accordingly. The benefit of this PR is increased consistency and standardization with the rest of the Jenkins ecosystem. If this PR is accepted, the next step would be to check in a
.git-blame-ignore-revsfile so that this commit doesn't clutter up the Git blame view.