[
https://issues.apache.org/jira/browse/HADOOP-8562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13667278#comment-13667278
]
Hudson commented on HADOOP-8562:
--------------------------------
Integrated in Hadoop-Yarn-trunk #221 (See
[https://builds.apache.org/job/Hadoop-Yarn-trunk/221/])
HADOOP-8562. Moved related jiras to 2.0.5 section in CHANGES.txt (Revision
1486336)
HADOOP-8562. Fix CHANGES.txt to move 8562 and related tasks to 2.0.5 section
(Revision 1486334)
Result = SUCCESS
suresh : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1486336
Files :
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
* /hadoop/common/trunk/hadoop-yarn-project/CHANGES.txt
suresh : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1486334
Files :
* /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt
> Enhancements to support Hadoop on Windows Server and Windows Azure
> environments
> -------------------------------------------------------------------------------
>
> Key: HADOOP-8562
> URL: https://issues.apache.org/jira/browse/HADOOP-8562
> Project: Hadoop Common
> Issue Type: New Feature
> Affects Versions: 3.0.0
> Reporter: Bikas Saha
> Assignee: Bikas Saha
> Fix For: 2.0.5-beta
>
> Attachments: branch-2.merge.patch, branch-2.merge.patch,
> branch-trunk-win.min-notest.patch, branch-trunk-win-min.patch,
> branch-trunk-win.min.patch, branch-trunk-win.patch, branch-trunk-win.patch,
> branch-trunk-win.patch, branch-trunk-win.patch, branch-trunk-win.patch,
> branch-trunk-win.patch, branch-trunk-win.patch, branch-trunk-win.patch,
> branch-trunk-win.patch, branch-trunk-win.patch, branch-trunk-win.patch,
> test-untar.tar, test-untar.tgz
>
>
> This JIRA tracks the work that needs to be done on trunk to enable Hadoop to
> run on Windows Server and Azure environments. This incorporates porting
> relevant work from the similar effort on branch 1 tracked via HADOOP-8079.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
