[ http://issues.apache.org/jira/browse/HADOOP-366?page=comments#action_12431003 ] James P. White commented on HADOOP-366: ---------------------------------------
A more comprehensive approach to the issue Thomas raises is to use a format that addresses all aspects of Java program execution dependency. The Java standard has two formats that address this in somewhat different ways: JNLP (Java Network Launch Protocol) http://java.sun.com/j2se/1.4.2/docs/guide/jws/index.html Used by Java Web Start. Addresses all of the Java platform execution issues, including using native code. But this is probably not the right level for packaing MapReduce modules, but rather should be used to package Hadoop itself. Extensions http://java.sun.com/j2se/1.4.2/docs/guide/extensions/index.html This is exactly what Thomas is asking for, and provides the format for included jars and the setting of the classpath. http://java.sun.com/j2se/1.4.2/docs/guide/extensions/spec.html Bundled Optional Packages The manifest for an application or optional package can specify one or more relative URLs referring to the JAR files and directories for the optional packages (and other libraries) that it needs. These relative URLs will be treated relative to the code base that the containing application or optional package JAR file was loaded from. An application (or, more generally, JAR file) specifies the relative URLs of the optional packages (and libraries) that it needs via the manifest attribute Class-Path. This attribute lists the URLs to search for implementations of optional packages (or other libraries) if they cannot be found as optional packages installed on the host Java virtual machine*. These relative URLs may include JAR files and directories for any libraries or resources needed by the application or optional package. Relative URLs not ending with '/' are assumed to refer to JAR files. For example, Class-Path: servlet.jar infobus.jar acme/beans.jar images/ Multiple Class-Path headers may be specified, and are combined sequentially. > 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
