[
https://issues.apache.org/jira/browse/HADOOP-14667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16093374#comment-16093374
]
Allen Wittenauer commented on HADOOP-14667:
-------------------------------------------
It's kind of a pain to upgrade the solution files. I wish Microsoft had made
devenv /upgrade be a bit smarter (e.g., no, I don't need backup files).
Additionally, I wish I knew more MSBuild to be able to craft something better
in the poms to do this work automatically, stick it in target, etc, etc. so
that the source tree doesn't get... wacky.
On the plus side, using this setup I'm able to build on VS 2013 on WS 2012. I
suspect it will mostly work with pretty much all builds of VS after manually
whacking away at the example command files with the appropriate settings. In
other words, we don't to necessarily upgrade the bundled files anymore and it
makes more sense to keep them at 2010 levels... with the assumption being that
users can go from 2010 -> modern, but not modern -> 2010.
> 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
>
>
> 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]
