Re: Re: [Fwd: Re: [JPackage-discuss] Re: Status of classpathx-mail, classpath-inetlib, gnu-crypto]

Ville Skyttä <[email protected]> writes:

> On Fri, 2004-08-13 at 00:31, Chris Burdess wrote:
>
>> A better solution would be to patch the manifest in the various jar 
>> files (gnumail.jar, gnumail-providers.jar, activation.jar, inetlib.jar) 
>> - - since the dependency jars have been installed to absolute locations 
>> by the package manager, you can simply insert a Class-Path entry in the 
>> manifest containing these absolute locations, and Java will locate the 
>> dependencies without the user having to specify a classpath explicitly.
>
> The current JPackage packaging policy forbids use of Class-Path in jar
> manifests altogether; we patch them out of them everywhere.  Despite of
> the Class-Path mechanism's inflexibility and inherent surprises, I am
> personally not necessarily a fan of that bit of the policy as a better
> 100% transparent mechanism does not really exist AFAIK.  Policy changes
> need discussion and time though, should they be required.

I wrote a classloader doing this but I don't think it's 1.1 compliant
but it works with free JDK's. It's been tested on kaffe, gij and I think
SableVM.

I'll make it a public project soon.

Cheers,

-- 
Arnaud Vandyck
http://fosdem.org/
Free and Open Source Software Developers' Meeting
February 26-27 2005,
Bruxelles, Belgium