hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Prashant Sharma (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-7726) eclipse plugin does not build with 0.24.0
Date Fri, 07 Oct 2011 05:46:29 GMT

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

Prashant Sharma commented on HADOOP-7726:

If this is for trunk version. You can read the BUILDING.txt in the top directory. 

for importing to eclipse you have two options. 

1) install m2-eclipse and import as existing maven project.
2) mvn eclipse:eclipse

I think the ant targets are no more used. The doc is old perhaps.

> eclipse plugin does not build with 0.24.0
> -----------------------------------------
>                 Key: HADOOP-7726
>                 URL: https://issues.apache.org/jira/browse/HADOOP-7726
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: contrib/eclipse-plugin
>    Affects Versions: 0.24.0
>         Environment: Fedora 15
>            Reporter: Tim Broberg
> I'm new to hadoop, java, and eclipse, so please forgive me if I jumble multiple issues
together or mistake the symptoms of one problem for a separate issue.
> Attempting to follow the build instructions from http://wiki.apache.org/hadoop/EclipseEnvironment,
the following commands are to be executed:
>   1 - mvn test -DskipTests
>   2 - mvn eclipse:eclipse -DdownloadSources=true -DdownloadJavadocs=true
>   3 - cd hdfs; ant compile eclipse
>   4 - cd ../; cd mapreduce; ant compile eclipse
> A - If "mvn test -DskipTests" is used for #1, #2 fails with "[ERROR] Failed to execute
goal on project hadoop-yarn-common: Could not resolve dependencies for project org.apache.hadoop:hadoop-yarn-common:jar:0.24.0-SNAPSHOT:"
> Per Luke Lu's suggestion, "mvn install -DskipTests -P-cbuild" instead of step #1 cleared
up this issue.
> B - For steps #3, and #4 there are no hdfs or mapreduce subdirectories. These appear
to have been renamed "hadoop-hdfs-project" and "hadoop-mapreduce-project".
> C - For step #3, if I then go to hadoop-hdfs-project instead and perform "ant compile
eclipse" no build.xml file is found - "Buildfile: build.xml does not exist!"
> D - For step #4, if I go to hadoop-mapreduce-project and do "ant compile eclipse" a set
of errors much like #A is produced:
> > [ivy:resolve]           ::::::::::::::::::::::::::::::::::::::::::::::
> > [ivy:resolve]           ::          UNRESOLVED DEPENDENCIES         ::
> > [ivy:resolve]           ::::::::::::::::::::::::::::::::::::::::::::::
> > [ivy:resolve]           ::
> > org.apache.hadoop#hadoop-yarn-server-common;0.24.0-SNAPSHOT: not found
> > [ivy:resolve]           ::
> > org.apache.hadoop#hadoop-mapreduce-client-core;0.24.0-SNAPSHOT: not found
> > [ivy:resolve]           ::
> > org.apache.hadoop#hadoop-yarn-common;0.24.0-SNAPSHOT: not found
> > [ivy:resolve]           ::::::::::::::::::::::::::::::::::::::::::::::
> E - If I ignore these issues and import the projects generated in step #2, I get a bunch
of errors related to the lack of an M2_REPO definition. Adding this variable needs to be included
in the build scripts or documentation in the wiki.
> F - Once that is resolved, eclipse shows hundreds of errors and warnings starting with
"AvroRecord" cannot be resolved to a type.
> Thanks so much for your work on this, but it needs a little more effort in documentation
and/or development before it is usable again.
> Thanks.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message