The Class-Path attribute of the manifest finds *external* JAR dependencies, not JARs inside the main JAR. And to come back on the attribute ordering in the manifest, the JAR spec. states in the "additional restrictions and rules that apply to manifest and signature files" section:
* The order of individual manifest entries is not significant. * The order of individual signature entries is not significant, except that the digests that get signed are in that order --DD -----Original Message----- From: Todd Wilson [mailto:[EMAIL PROTECTED]] Sent: Wednesday, March 13, 2002 9:31 AM To: Ant Users List Subject: Re: Using Main-Class and Class-Path in a manifest file Many thanks to those who have offered suggestions. We'll experiment with the various options and settle on something. Todd Diane Holt wrote: > --- Todd Wilson <[EMAIL PROTECTED]> wrote: > >>It's not an absolute necessity for us to include everything in a single >>jar file, but it is a convenience. >> > > Would there be a problem with sticking the individual log4j files into > your jar (as opposed to putting them in as a jar themselves)? If you did > that then it should work (right?), and you'd still have a single jar file. > > Diane > > ===== > ([EMAIL PROTECTED]) > > > > __________________________________________________ > Do You Yahoo!? > Try FREE Yahoo! Mail - the world's greatest free email! > http://mail.yahoo.com/ > > -- 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]>
