[
https://issues.apache.org/jira/browse/HADOOP-17952?focusedWorklogId=660485&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-660485
]
ASF GitHub Bot logged work on HADOOP-17952:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 05/Oct/21 17:47
Start Date: 05/Oct/21 17:47
Worklog Time Spent: 10m
Work Description: virajjasani edited a comment on pull request #3503:
URL: https://github.com/apache/hadoop/pull/3503#issuecomment-934619131
> On the other hand,Pushing those changes after a major milestone would mean
only one Jira and one PR (i.e., HADOOP-XYZ: migrating banned imports to use
restrict-imports-enforcer-rule).
IMHO the problem here is that if someone has already pushed a couple of
commits with illegal imports by the time we are done with all modules, then we
will have to take care of such individual modules violating the rule (by
replacing the respective imports), it's kind of rework right?
--
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: 660485)
Time Spent: 2h (was: 1h 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
> Time Spent: 2h
> 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]
