This is the mail archive of the
mailing list for the Mauve project.
Re: Eclipse and Classpath
- From: Tom Tromey <tromey at redhat dot com>
- To: Thomas Zander <zander at javalobby dot org>
- Cc: mauve-discuss at sources dot redhat dot com,Jeff Sturm <jsturm at one-point dot com>, Michael Koch <konqueror at gmx dot de>
- Date: 30 Apr 2004 17:11:27 -0600
- Subject: Re: Eclipse and Classpath
- References: <Pine.LNX.email@example.com><firstname.lastname@example.org><email@example.com>
- Reply-to: tromey at redhat dot com
>>>>> "Thomas" == Thomas Zander <firstname.lastname@example.org> writes:
Thomas> IIRC the biggest problem with using JUnit is that it depends
Thomas> of rather advanced JVM features; like reflection.
Yeah. However, Mauve already uses Class.forName and
Class.newInstance, so it is already relying on some reflection
Also, when Mauve was started, gcj limitations drove some of the design
decisions. In particular we set things up carefully to avoid
functionality we knew would not work with gcj. Since then things have
changed; all the free VMs are much more capable.