[ http://issues.apache.org/jira/browse/HADOOP-366?page=comments#action_12431629 ] James P. White commented on HADOOP-366: ---------------------------------------
I don't think WAR layout really applies here, and I do think packaging jobs as a JAR make sense. WAR is for an application, not a library/fragment. The application packaging I'ld like to see for Hadoop is JNLP (Java Web Start). For the situation where common jars are used by multiple job instances, the Extension mechanism supports job jars which are simply a configuration file and dependency(s) on application jars: http://java.sun.com/j2se/1.4.2/docs/guide/extensions/spec.html#deployment And as for job jars being executable or not, they certainly are executables from Hadoop's perspective. And while Hadoop packaging needs its own issue, I'll point out that putting the dependencies in the job jar to launch Hadoop for the job if it is executed might be a reasonable choice. > Should be able to specify more than one jar into a JobConf file > --------------------------------------------------------------- > > Key: HADOOP-366 > URL: http://issues.apache.org/jira/browse/HADOOP-366 > Project: Hadoop > Issue Type: Improvement > Components: mapred > Affects Versions: 0.4.0 > Reporter: Thomas FRIOL > > A job should be able to specify more than one jar file into its JobConf file > because sometimes custom Map and Reduce classes or just InputFormat classes > uses objects coming from other jar files. For now, we have to build a unique > jar to make Hadoop mapreduce operations works. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
