This is the mail archive of the
mailing list for the Mauve project.
RE: Some issues..
- From: "Jeroen Frijters" <jeroen at sumatra dot nl>
- To: "Mark Wielaard" <mark at klomp dot org>,"Andrew Haley" <aph at redhat dot com>
- Cc: "Thomas Zander" <zander at javalobby dot org>,<mauve-discuss at sources dot redhat dot com>
- Date: Fri, 23 Apr 2004 11:11:52 +0200
- Subject: RE: Some issues..
Mark Wielaard wrote:
> On Fri, 2004-04-16 at 14:03, Andrew Haley wrote:
> > Mark Wielaard writes:
> > > Ehe, how do you use/invoke it?
> > It gets invoked automatically when you run Mauve, at least on my
> > system. BinaryCompatibilityTest.java is the driver that invokes it.
> Aha. And it uses Runtime.exec()... Which wasn't properly
> implemented in GNU Classpath proper. But we have it now (almost)!
> ow that I can run it I see that kaffe, jamvm and gij all fail most of
> the tests. Each of IL bin_01 till IL bin_18 fails 5 or 6 times giving:
> 107 of 125 tests failed
I never really payed attention to this test, but now I see that it is
*nix specific (using shell script <shiver>).
What is the policy for Mauve? I realise most of you don't care about/for
Windows, but personally I do. So I support Mark's earlier
suggestion/request to move this to a separate section.
On a somewhat related note, the invalid_port test in DatagramSocketTest2
assumes that it is illegal to create a DatagramSocket that listens on
port 21, but I don't believe that is part of the Java specification.