beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tim Robertson (JIRA)" <>
Subject [jira] [Closed] (BEAM-4350) Enforce ErrorProne analysis in the mqtt IO project
Date Fri, 18 May 2018 14:44:00 GMT


Tim Robertson closed BEAM-4350.
       Resolution: Duplicate
    Fix Version/s: 2.5.0

The title says MQTT and the body refers to MongoDB but those issues both exist elsewhere.

Suspect this was just done in error when opening many issues as clones.

CC [~swegner] in case I'm overlook something.

> Enforce ErrorProne analysis in the mqtt IO project
> --------------------------------------------------
>                 Key: BEAM-4350
>                 URL:
>             Project: Beam
>          Issue Type: Improvement
>          Components: io-java-mongodb
>            Reporter: Scott Wegner
>            Assignee: Tim Robertson
>            Priority: Minor
>              Labels: errorprone, starter
>             Fix For: 2.5.0
> Java ErrorProne static analysis was [recently enabled|]
in the Gradle build process, but only as warnings. ErrorProne errors are generally useful
and easy to fix. Some work was done to [make sdks-java-core ErrorProne-clean|]
and add enforcement. This task is clean ErrorProne warnings and add enforcement in {{beam-sdks-java-io-mongodb}}.
Additional context discussed on the [dev list|].
> Fixing this issue will involve:
> # Follow instructions in the [Contribution Guide|]
to set up a {{beam}} development environment.
> # Run the following command to compile and run ErrorProne analysis on the project: {{./gradlew
> # Fix each ErrorProne warning from the {{sdks/java/io/mongodb}} project.
> # In {{sdks/java/io/mongodb/build.gradle}}, add {{failOnWarning: true}} to the call the
{{applyJavaNature()}} ([example|]).
> This starter issue is sponsored by [~swegner]. Feel free to [reach out|]
with questions or code review:
> * JIRA: [~swegner]
> * GitHub: [@swegner|]
> * Slack: [@Scott Wegner|]
> * Email: swegner at google dot com

This message was sent by Atlassian JIRA

View raw message