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

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

                Author: ASF GitHub Bot
            Created on: 07/Oct/21 13:01
            Start Date: 07/Oct/21 13:01
    Worklog Time Spent: 10m 
      Work Description: virajjasani commented on pull request #3503:
URL: https://github.com/apache/hadoop/pull/3503#issuecomment-937769502


   > I'm still not sure if VisibleForTesting should be replaced in the lower 
branches. If we do it, I think it's ok to do the replacements in all modules at 
once for the lower branches, instead of proceeding with the replacements in 
each individual module.
   
   Sounds good @tasanuma


-- 
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.

To unsubscribe, e-mail: [email protected]

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


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

    Worklog Id:     (was: 661591)
    Time Spent: 5h  (was: 4h 50m)

> Replace Guava VisibleForTesting by Hadoop's own annotation in 
> hadoop-common-project modules
> -------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-17952
>                 URL: https://issues.apache.org/jira/browse/HADOOP-17952
>             Project: Hadoop Common
>          Issue Type: Sub-task
>            Reporter: Viraj Jasani
>            Assignee: Viraj Jasani
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 3.4.0
>
>          Time Spent: 5h
>  Remaining Estimate: 0h
>




--
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