Re: java dependency substvars and native compilation
- To: email@example.com
- Subject: Re: java dependency substvars and native compilation
- From: "Arnaud Vandyck" <firstname.lastname@example.org>
- Date: Fri, 20 Jul 2007 10:17:02 +0200
- Message-id: <[🔎] email@example.com>
- In-reply-to: <20070511170940.GG18640@nephtys.trinhall.cam.ac.uk>
- References: <20070502125846.GP3770@nephtys.trinhall.cam.ac.uk> <firstname.lastname@example.org> <20070503080012.GK3100@mail.konqueror.de> <email@example.com> <20070510131127.GP18640@nephtys.trinhall.cam.ac.uk> <20070511051906.GB3100@mail.konqueror.de> <20070511170940.GG18640@nephtys.trinhall.cam.ac.uk>
On 5/11/07, Matthew Johnson <firstname.lastname@example.org> wrote:
On Fri May 11 07:19, Michael Koch wrote:
> On Thu, May 10, 2007 at 02:11:27PM +0100, Matthew Johnson wrote:
> > OK, so as an alternative, I have a version which reads the Class-Path:
> > variable from the jar.
> Setting the Class-Path attribute in the manifest only makes sense for
> applications. It doesn't makes sense for libraries. The problem is that
> the VM only uses the Class-Path attribute when you execute
It also makes sense for libraries; Java recursively adds the classpath,
so a library which depended on other libraries would have one so that
applications don't have to guess what libraries their libraries may use.
This is true if the application is launched with java -jar myapp.jar.
Any way, setting Class-Path property in the MANIFEST file is a very good idea.