[ 
https://issues.apache.org/jira/browse/HADOOP-9489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14546318#comment-14546318
 ] 

Ravi Prakash commented on HADOOP-9489:
--------------------------------------

Thanks for the patches Chris! I use Eclipse and I am able to import the 
projects without this patch. I *do* build the project before running mvn 
eclipse:eclipse, so I'm a +1 to adding that in BUILDING.txt. We should probably 
also level expectations (some newcomers may expect to be able to build and 
"run" the project from Eclipse; I've never been able to do this) I find Eclipse 
immensely useful for navigating the code, attaching remote debuggers and 
stepping through, but I build and run only on the command line using mvn . I 
wonder if that is other peoples' process too?

> 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
>              Labels: BB2015-05-TBR
>         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)

Reply via email to