[
https://issues.apache.org/jira/browse/HADOOP-9489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13638027#comment-13638027
]
Robert Joseph Evans commented on HADOOP-9489:
---------------------------------------------
I am not really sure that we want to require m2eclipse plug-in. It the past
using mvn eclipse:eclipse and the m2plugin caused conflicts with one another,
although recently there have not been as many issues with that.
http://maven.apache.org/plugins/maven-eclipse-plugin/
has instructions on how to use the maven-eclipse-plugin. This is what is run
when you run eclipse:eclipse. You can set M2_REPO manually inside eclipse, or
you can run mvn eclipse:configure-workspace to set the M2_REPO. Please refer to
http://maven.apache.org/plugins/maven-eclipse-plugin/configure-workspace-mojo.html
for more details about that command because you may need to define some other
parameters on the command line to make it work properly with your environment.
> 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: 3.0.0
> Reporter: Carl Steinbach
> Assignee: Chris Nauroth
> Attachments: eclipse_hadoop_errors.txt, HADOOP-9489.1.patch
>
>
> 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 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
