[
https://issues.apache.org/jira/browse/HADOOP-9489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14343589#comment-14343589
]
Hadoop QA commented on HADOOP-9489:
-----------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12701924/HADOOP-9489.004.patch
against trunk revision ca1c00b.
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. There were no new javadoc warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
hadoop-common-project/hadoop-common.
Test results:
https://builds.apache.org/job/PreCommit-HADOOP-Build/5814//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/5814//console
This message is automatically generated.
> Eclipse instructions in BUILDING.txt don't work
> -----------------------------------------------
>
> Key: HADOOP-9489
> URL: https://issues.apache.org/jira/browse/HADOOP-9489
> Project: Hadoop Common
> Issue Type: Bug
> Components: build
> Affects Versions: 2.7.0
> Reporter: Carl Steinbach
> Priority: Minor
> Attachments: HADOOP-9489.003.patch, HADOOP-9489.004.patch,
> HADOOP-9489.1.patch, HADOOP-9489.2.patch, eclipse_hadoop_errors.txt, error.log
>
>
> I have tried several times to import Hadoop trunk into Eclipse following the
> instructions in the BUILDING.txt file, but so far have not been able to get
> it to work.
> If I use a fresh install of Eclipse 4.2.2, Eclipse will complain about an
> undefined M2_REPO environment variable. I discovered that this is defined
> automatically by the M2Eclipse plugin, and think that the BUILDING.txt doc
> should be updated to explain this.
> After installing M2Eclipse I tried importing the code again, and now get over
> 2500 errors related to missing class dependencies. Many of these errors
> correspond to missing classes in the oah*.proto namespace, which makes me
> think that 'mvn eclipse:eclipse' is not triggering protoc.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
