Skip to content
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

Upgrade gradle-errorprone #1371

Merged
merged 6 commits into from
Jun 1, 2020
Merged

Upgrade gradle-errorprone #1371

merged 6 commits into from
Jun 1, 2020

Conversation

ferozco
Copy link
Contributor

@ferozco ferozco commented Jun 1, 2020

Before this PR

We had blocked upgrades of gradle-errorprone because we were worried about forcing a "high" dependency on gradle (5.2). Since then gradle has released a bunch and the fleet has been keeping up to date so we no longer have to be worried about the dependency.

After this PR

==COMMIT_MSG==
Upgrade gradle-errorprone
==COMMIT_MSG==

Possible downsides?

N/A

@changelog-app
Copy link

changelog-app bot commented Jun 1, 2020

Generate changelog in changelog/@unreleased

Type

  • Feature
  • Improvement
  • Fix
  • Break
  • Deprecation
  • Manual task
  • Migration

Description

Upgrade gradle-errorprone

Check the box to generate changelog(s)

  • Generate changelog entry

@ferozco
Copy link
Contributor Author

ferozco commented Jun 1, 2020

Ya I noticed :( its quite unfortunate since its pretty common for people to configure checks that way. I think we may want to hold off on merging this until we have a replacement. My current thoughts are to propose the following to the upstream plugin:

tasks.withType(JavaCompile) {
  options.errorprone.check 'OptionalOrElseMethodInvocation', 'OFF'
}

Eh, actually looking at it they already expose pretty nice methods configuring checks. ex:

@robert3005
Copy link
Contributor

yeah, I think current version of the plugin has nice apis. Just the original version only really had the array based method and we stuck to it.

README.md Outdated Show resolved Hide resolved
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants