[
https://issues.apache.org/jira/browse/FALCON-382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13950460#comment-13950460
]
Sunil Kumar commented on FALCON-382:
------------------------------------
HI [~s_venkatesh] ,
Following is the classpath of Hadoop 2.2.0:
/usr/share/hadoop/hadoop-2.2.0/etc/hadoop:/usr/share/hadoop/hadoop-2.2.0/share/hadoop/common/lib/*:/usr/share/hadoop/hadoop-2.2.0/share/hadoop/common/*:/usr/share/hadoop/hadoop-2.2.0/share/hadoop/hdfs:/usr/share/hadoop/hadoop-2.2.0/share/hadoop/hdfs/lib/*:/usr/share/hadoop/hadoop-2.2.0/share/hadoop/hdfs/*:/usr/share/hadoop/hadoop-2.2.0/share/hadoop/yarn/lib/*:/usr/share/hadoop/hadoop-2.2.0/share/hadoop/yarn/*:/usr/share/hadoop/hadoop-2.2.0/share/hadoop/mapreduce/lib/*:/usr/share/hadoop/hadoop-2.2.0/share/hadoop/mapreduce/*:/usr/share/hadoop/hadoop-2.2.0/contrib/capacity-scheduler/*.jar
But i have one question when we build Falcon with hadoop2 profile. All the
library of the Hadoop2 already get copied to the FALCON_HOME/hadooplibs/ . So
rather than pointing Falcon to the hadoop2 actual classpath pointing it to
FALCON_HOME/hadooplibs/* will be better because if we want to install Falcon on
separate node rathor than on hadoop node itself will make it possible. Please
[~shwethags] validate my understanding if you are align to my suggestions as
well..
> Error While building Latest trunk code with Hadoop 2.2.0
> --------------------------------------------------------
>
> Key: FALCON-382
> URL: https://issues.apache.org/jira/browse/FALCON-382
> Project: Falcon
> Issue Type: Bug
> Components: build-tools, oozie
> Affects Versions: 0.5
> Environment: Centos 6.3 and Hadoop 2.2.0
> Reporter: Sunil Kumar
> Assignee: Suhas Vasu
> Priority: Blocker
>
> Hi,
> Today pulled latest code from the git and trying to build with hadoop 2.2.0.
> Following are the details:
> Maven Command: mvn clean install -Phadoop-2 -Doozie.version=4.0.0 -DskipTests
> Error on Console:
> ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.2.1:exec
> (BUILD-OOZIE) on project build-tools: Command execution failed. Process
> exited with an error: 1 (Exit value: 1) -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.codehaus.mojo:exec-maven-plugin:1.2.1:exec (BUILD-OOZIE) on project
> build-tools: Command execution failed.
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:216)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:108)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:76)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:116)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:361)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:213)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:157)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> Caused by: org.apache.maven.plugin.MojoExecutionException: Command execution
> failed.
> at org.codehaus.mojo.exec.ExecMojo.execute(ExecMojo.java:362)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:133)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> ... 19 more
> Caused by: org.apache.commons.exec.ExecuteException: Process exited with an
> error: 1 (Exit value: 1)
> at
> org.apache.commons.exec.DefaultExecutor.executeInternal(DefaultExecutor.java:377)
> at
> org.apache.commons.exec.DefaultExecutor.execute(DefaultExecutor.java:160)
> at
> org.codehaus.mojo.exec.ExecMojo.executeCommandLine(ExecMojo.java:610)
> at org.codehaus.mojo.exec.ExecMojo.execute(ExecMojo.java:352)
> ... 21 more
> [ERROR]
--
This message was sent by Atlassian JIRA
(v6.2#6252)