--- Godmar Back <[EMAIL PROTECTED]> wrote:
> >
> > [jsantala@yavin bin]$ export CLASSPATH=foobar.jar
> > [jsantala@yavin bin]$ jar
> >
> > In other words, Kaffe appears to fail/crash
> silently if it can't find any
> > component in the CLASSPATH (And this appears to
> include classpaths
> > spe
Hi Godmar,
--- Godmar Back <[EMAIL PROTECTED]> wrote:
> Other than that, Kaffe's classpath handling is
> exactly that of JDK 1.1.
> My understanding is that Dalibor is working on
> updating to 1.2 behavior,
> but the current kaffe (or at least the version I
> looked at last)
> did or used to do 1
>
> [jsantala@yavin bin]$ export CLASSPATH=foobar.jar
> [jsantala@yavin bin]$ jar
>
> In other words, Kaffe appears to fail/crash silently if it can't find any
> component in the CLASSPATH (And this appears to include classpaths
> specified in jar files, making most pre-bundled jar-files unusabl
antala" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, May 06, 2002 6:19 AM
Subject: [kaffe] Poor CLASSPATH handling...
> [jsantala@yavin bin]$ export CLASSPATH=foobar.jar
> [jsantala@yavin bin]$ jar
>
> In other words, Kaffe appears to fail/crash silently if it
[jsantala@yavin bin]$ export CLASSPATH=foobar.jar
[jsantala@yavin bin]$ jar
In other words, Kaffe appears to fail/crash silently if it can't find any
component in the CLASSPATH (And this appears to include classpaths
specified in jar files, making most pre-bundled jar-files unusable). It
appears
