[ 
https://issues.apache.org/jira/browse/HADOOP-17269?focusedWorklogId=498619&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-498619
 ]

ASF GitHub Bot logged work on HADOOP-17269:
-------------------------------------------

                Author: ASF GitHub Bot
            Created on: 09/Oct/20 15:28
            Start Date: 09/Oct/20 15:28
    Worklog Time Spent: 10m 
      Work Description: aajisaka commented on pull request #2374:
URL: https://github.com/apache/hadoop/pull/2374#issuecomment-706247983


   Merged. Thank you @iwasakims 


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[email protected]


Issue Time Tracking
-------------------

    Worklog Id:     (was: 498619)
    Time Spent: 1h  (was: 50m)

> [JDK 11] False-positive findbugs warnings
> -----------------------------------------
>
>                 Key: HADOOP-17269
>                 URL: https://issues.apache.org/jira/browse/HADOOP-17269
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: build
>            Reporter: Akira Ajisaka
>            Assignee: Akira Ajisaka
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 1h
>  Remaining Estimate: 0h
>
> In Java 11, there are a lot of false-positive findbugs warnings in 
> try-with-resources.
> Ref: 
> https://ci-hadoop.apache.org/job/hadoop-qbt-trunk-java11-linux-x86_64/1/artifact/out/branch-findbugs-hadoop-common-project_hadoop-common-warnings.html
> This issue has been fixed by https://github.com/spotbugs/spotbugs/pull/1248 
> but now there are no releases that include this fix.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to