beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Work logged] (BEAM-4356) Enforce ErrorProne analysis in the nexmark project
Date Thu, 31 May 2018 07:45:00 GMT


ASF GitHub Bot logged work on BEAM-4356:

                Author: ASF GitHub Bot
            Created on: 31/May/18 07:44
            Start Date: 31/May/18 07:44
    Worklog Time Spent: 10m 
      Work Description: iemejia commented on a change in pull request #5513: [BEAM-4356] Enforce
ErrorProne analysis in nexmark

 File path: sdks/java/nexmark/src/main/java/org/apache/beam/sdk/nexmark/
 @@ -25,6 +25,7 @@
  * A set of {@link NexmarkConfiguration}s.
 Review comment:
   I agree that the idea of fixing errorprone issues is not to just mark things to be ignored,
but here there is a bigger issue.  This change is not so simple, at the first try I just changed
the Lists to be immutable, but errorprone requires the type of the object in the list [to
be immutable too](
   So fixing this implies making `NexmarkConfiguration` an Immutable object and this has a
considerable impact so I prefer that this is covered in a different ticket (also to address
the repeated options with NexmarkOptions). I just created [BEAM-4433](
for this. Feel free to take it @cademarkegard if you are interested on working on it.

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:

Issue Time Tracking

    Worklog Id:     (was: 107592)
    Time Spent: 50m  (was: 40m)

> Enforce ErrorProne analysis in the nexmark project
> --------------------------------------------------
>                 Key: BEAM-4356
>                 URL:
>             Project: Beam
>          Issue Type: Improvement
>          Components: examples-nexmark
>            Reporter: Scott Wegner
>            Assignee: Ismaël Mejía
>            Priority: Minor
>              Labels: errorprone, starter
>          Time Spent: 50m
>  Remaining Estimate: 0h
> 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-nexmark}}.
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/nexmark}} project.
> # In {{sdks/java/nexmark/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