Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!aioe.org!eternal-september.org!feeder.eternal-september.org!.POSTED!not-for-mail From: markspace <-@.> Newsgroups: comp.lang.java.programmer Subject: Re: Linking Jars Date: Sun, 04 Dec 2011 13:43:55 -0800 Organization: A noiseless patient Spider Lines: 12 Message-ID: References: <9k0vruFa01U1@mid.individual.net> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Injection-Date: Sun, 4 Dec 2011 21:43:57 +0000 (UTC) Injection-Info: mx04.eternal-september.org; posting-host="XjIWM99mD7Ijfdu600oVPA"; logging-data="5743"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX19pIC7/YeEf3yKJZeqSfDVEDdCcCBOKoPI=" User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0) Gecko/20111105 Thunderbird/8.0 In-Reply-To: Cancel-Lock: sha1:tybIQxs/SSmMUxu403lZjXXHGbs= Xref: x330-a1.tempe.blueboxinc.net comp.lang.java.programmer:10497 On 12/4/2011 12:25 PM, Tom Anderson wrote: > The problem is that the Class-Path header expresses the dependency as a > URL; a direct path that can be resolved in the filesystem. I thought class path entries in the manifest file were always relative to the location of the containing Jar file? I guess you could specify an absolute path, but I don't think it's required. I didn't check the docs, but that's afaik.