Skip to content
This repository has been archived by the owner on Jul 1, 2022. It is now read-only.

Use the verify task in google-formatter instead of checkstyle #55

Merged
merged 1 commit into from
Sep 20, 2016

Conversation

vprithvi
Copy link
Contributor

  • The checkstyle checks weren't 100pc in sync with the formatter
    checks, so we solely rely on the formatter's checks
  • The build now fails if code isn't formatted correctly

- The checkstyle checks weren't 100pc in sync with the formatter
  checks, so we solely rely on the formatter's checks
- The build now fails if code isn't formatted correctly
@@ -14,7 +14,6 @@ ext.apacheThriftVersion = '0.9.3'
ext.jerseyVersion = '2.22.2'
ext.slf4jVersion = '1.7.16'
ext.jacksonVersion = '2.7.4'
ext.checkstyleVersion = '7.1.1'
Copy link
Member

@yurishkuro yurishkuro Sep 19, 2016

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I thought checkstyle checks not just the formatting, but the actual code mistakes, like go vet

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think checkstyle is that intelligent. Findbugs is more similar to go vet
From wikipedia,

The performed checks mainly limit themselves to the presentation and don't analyze content, and do not confirm the correctness or completeness of the program.

@vprithvi vprithvi merged commit 9df7efc into master Sep 20, 2016
@vprithvi vprithvi deleted the use_google_formatter branch September 20, 2016 15:40
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants