Hello Jens, We have seen spurious failures from mvn eclipse:eclipse like this in the past. I recommend that you enter a comment on MAPREDUCE-6320 stating that you tested mvn eclipse:eclipse locally and it ran fine.
BTW, we're nearly ready to commit a major rewrite of our pre-commit build automation in HADOOP-11746. Let's see if the problems subside after that. For now, I don't think it's worthwhile to investigate this failure any further. Thank you for following up! Chris Nauroth Hortonworks http://hortonworks.com/ On 4/20/15, 12:28 PM, "Jens Rabe" <[email protected]> wrote: >Hello! > >I just submitted a patch for MAPREDUCE-6320 and Hadoop QA said it failed >to build with eclipse:eclipse. I looked in the console output from the >build and indeed there is a suspicious output: > >/home/jenkins/tools/maven/latest/bin/mvn eclipse:eclipse >-DHadoopPatchProcess > >/home/jenkins/jenkins-slave/workspace/PreCommit-MAPREDUCE-Build/../patchpr >ocess/patchEclipseOutput.txt 2>&1 >/home/jenkins/jenkins-slave/workspace/PreCommit-MAPREDUCE-Build/dev-suppor >t/test-patch.sh: line 696: >/home/jenkins/jenkins-slave/workspace/PreCommit-MAPREDUCE-Build/../patchpr >ocess/patchEclipseOutput.txt: No such file or directory > >I ran mvn eclipse:eclipse -DHadoopPatchProcess manually on my computer >and it worked. Is this warning related to my patch or is this another >issue? mvn apache-rat:check also reports some „no such file or directory“.
