classpath
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[PATCH] Mauve is too hard to run.


From: Thomas Zander
Subject: [PATCH] Mauve is too hard to run.
Date: Thu, 1 Apr 2004 10:37:17 +0200
User-agent: KMail/1.6.1

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I think that there are 2 distinct user groups for the 'mauve' tool. One is 
the JVM developers which need to use the lowest common dominator in Java 
implementations. So it runs on a minimal Java implementation.

The other group is where I find myself in; the group that has extensive 
experience with Java, its huge toolset and can't imagine working on a 
halve-implemented JVM.
For that latter group the automake-autoconf toolset is just too hard to 
use.

Because of that I created an ant-task including an ant build file which 
means absolutely no CLI usage is needed to start running the mauve test 
suite.
The ant-based runnables assumes a fully implemented JVM and therefor uses a 
completely seperate buildflow from the 'make' equivalent. You can run ant 
and then run make to test 2 seperate JVMs, for example.

Can someone please commit these files/diff to the mauve test suite?

ps. notice that this makes the Mauve toolset immidiately Windows 
compatible...

Cheers!
- -- 
Thomas
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFAa9TACojCW6H2z/QRAs3YAJ9h3zFwA9o9Q+OKhOazFgLjo810CgCffj3t
zEZfhDMM1RKIj/nOA8XI4JQ=
=n9L8
-----END PGP SIGNATURE-----

Attachment: antMauve.tgz
Description: application/tgz


reply via email to

[Prev in Thread] Current Thread [Next in Thread]