Re: Linking Jars
On Sun, 4 Dec 2011, markspace wrote:
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?
Yep. They're relative URLs! The spec says
Class-Path: The value of this attribute specifies the relative URLs of
the extensions or libraries that this application or extension needs.
URLs are separated by one or more spaces. The application or extension
class loader uses the value of this attribute to construct its internal
search path.
I guess you could specify an absolute path, but I don't think it's
required.
Indeed it's not. But a relative URL is still a URL.
tom
--
I'd better quit my talking, 'cause I told you all I know. But please
remember, pardner, wherever you may go: the people are building a peaceful
world, and when the job is done, that'll be the biggest thing that man
has ever done.