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

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

                Author: ASF GitHub Bot
            Created on: 01/Oct/21 06:44
            Start Date: 01/Oct/21 06:44
    Worklog Time Spent: 10m 
      Work Description: virajjasani opened a new pull request #3505:
URL: https://github.com/apache/hadoop/pull/3505


   ### Description of PR
   Provide alternative to Guava VisibleForTesting so that we can get rid of 
Guava dependency to represent testing scope for a class/method/field.


-- 
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: 658763)
    Time Spent: 2h  (was: 1h 50m)

> Provide alternative to Guava VisibleForTesting in Hadoop common
> ---------------------------------------------------------------
>
>                 Key: HADOOP-17947
>                 URL: https://issues.apache.org/jira/browse/HADOOP-17947
>             Project: Hadoop Common
>          Issue Type: Sub-task
>            Reporter: Viraj Jasani
>            Assignee: Viraj Jasani
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 2h
>  Remaining Estimate: 0h
>
> In an attempt to reduce the dependency on Guava, we should remove 
> VisibleForTesting annotation usages as it has very high usage in our 
> codebase. This Jira is to provide Hadoop's own alternative and use it in 
> hadoop-common-project modules.



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