It's not an absolute necessity for us to include everything in a single jar file, but it is a convenience. In the jar spec it seems to hint at the fact that you can do this, though I'm inferring that. It doesn't seem to be very explicit about it.
Anyway, if we're trying to make the java runtime do something that it wasn't necessarily designed to do then you're probably right--we may just be better off deploying the dependency jars separately and simply referring to them still in the classpath in the manifest file. Todd Rod Mackenzie wrote: > Todd, > > I don't think you should include you log4j.jar iin your > HelloWorld.jar, I can't find any info on whether a jar will be seached > for other jars when searching for a class. I have tried a similar test > to yours using the Main-Class and Class-Path and didn't have a problem > but I didn't package all the jars into one. > > Rod > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
