[ http://issues.apache.org/jira/browse/HADOOP-366?page=comments#action_12431620 ] Doug Cutting commented on HADOOP-366: -------------------------------------
Sorry, I wasn't arguing that job jar's conform to the war file spec, rather that, if we're looking for sucessful methods of including libraries in jar files, the war file provides a good analogy, one that is more widely used than executable jars. A job jar is not an executable jar. It is not standalone: it always gets the hadoop classes externaly, from the environment it is loaded into. In this way it is like a war file, which always gets servlet runtime from the servlet runner. A job jar is not a war file: it doesn't specify servlets, include jsp pages, etc. The reason for the WEB-INF directory in a war file is to hide these files, so that, by default, files in the war are web pages, image files, etc. to be served, unless they're in WEB-INF. > 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
