This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
Re: Classpath vs java.class.path
- From: Jeff Sturm <jsturm at one-point dot com>
- To: Mark Wielaard <mark at klomp dot org>
- Cc: Steve Pribyl <steve at netfuel dot com>, <tromey at redhat dot com>, gcj mail list <java at gcc dot gnu dot org>
- Date: Wed, 16 Jul 2003 18:39:29 -0400 (EDT)
- Subject: Re: Classpath vs java.class.path
On 17 Jul 2003, Mark Wielaard wrote:
> You could integrate that with libgcj and let VMClassLoader only handle
> the bootstrap classpath and then have the SystemClassLoader (with
> VMClassLoader as parent) handle the user classpath (and the system
> property).
Sounds good. I'd like to slim down gnu.gcj.runtime.VMClassLoader anyway,
and make it more like a real bootstrap loader. As it is now, it pulls in
way too much of the runtime. Not so good for embedded apps.
Jeff