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

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

                Author: ASF GitHub Bot
            Created on: 28/Jul/22 12:08
            Start Date: 28/Jul/22 12:08
    Worklog Time Spent: 10m 
      Work Description: GauthamBanasandra commented on PR #4616:
URL: https://github.com/apache/hadoop/pull/4616#issuecomment-1198055884

   The vcxproj and solution files automatically get retargeted due to 
-https://github.com/apache/hadoop/blob/95a85875d0038a73f7e6c2cdb6efdc5132d63beb/hadoop-common-project/hadoop-common/pom.xml#L844-L923
   
   I'm able to build the trunk on Windows without this PR -
   
![image](https://user-images.githubusercontent.com/10280768/181501201-5d0ff992-7d0c-4e1b-8f2b-88fee773b6ac.png)
   
   
   Closing this PR since these changes are not needed.




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

    Worklog Id:     (was: 796050)
    Time Spent: 2h 50m  (was: 2h 40m)

> Retarget solution file to VS2019
> --------------------------------
>
>                 Key: HADOOP-18357
>                 URL: https://issues.apache.org/jira/browse/HADOOP-18357
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: common
>    Affects Versions: 3.4.0
>         Environment: Windows 10
>            Reporter: Gautham Banasandra
>            Assignee: Gautham Banasandra
>            Priority: Major
>              Labels: libhdfscpp, pull-request-available
>          Time Spent: 2h 50m
>  Remaining Estimate: 0h
>
> The Visual Studio version used by winutils and native components in Hadoop 
> common are quite old. We need to retarget the solution and vcxproj files to 
> use the latest version (Visual Studio 2019 as of this writing).



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

Reply via email to