[
https://issues.apache.org/jira/browse/HADOOP-14667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16107724#comment-16107724
]
Allen Wittenauer commented on HADOOP-14667:
-------------------------------------------
bq. Does this mean the build will modify files that committers have to remember
to unstage before commit?
That's exactly what that means. devenv upgrades the solution (sln) and VS
project (vxcproj) files for the new version. From what I can tell, it's usually
just updating the XML schema version and setting some version flags. (It's
sort of ridiculous really, but whatever.) There's also the backup dirs and logs
it creates. All of those changes stick out when doing a git diff or a git
status.
But yeah, with a bit more work, I'm fairly confident I can get an "on the fly"
upgrade-in-place. Only requirement would be that vcvarsall be run one time
prior to doing any maven work so that the paths are established.
> Flexible Visual Studio support
> ------------------------------
>
> Key: HADOOP-14667
> URL: https://issues.apache.org/jira/browse/HADOOP-14667
> Project: Hadoop Common
> Issue Type: Improvement
> Components: build
> Affects Versions: 3.0.0-beta1
> Environment: Windows
> Reporter: Allen Wittenauer
> Assignee: Allen Wittenauer
> Attachments: HADOOP-14667.00.patch, HADOOP-14667.01.patch,
> HADOOP-14667.02.patch, HADOOP-14667.03.patch, HADOOP-14667.04.patch
>
>
> Is it time to upgrade the Windows native project files to use something more
> modern than Visual Studio 2010?
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
