>I don't know if anyone besides Aaron has really done much with mauve.
>I need to download that and see what kind of bugs can be found with
>what we currently have, or tests I can possibly make.
Mauve is a fairly easy framework to use. I've put some of my java.io tests
into the archive, which are in gnu/testlet/java/io. You can use those as
examples. After configuring, you do a "make check" to run the tests. There
are some problems with the Mauve build setup/running the tests which need to
be fixed, but should be easy to hack around. People writing tests should be
using this framework to do so. And you are writing tests, right?
>Need to get all the todo lists updated and documentation fixed up for
>the first release, along with sending in my own copyright assignment
>papers.
>
>Need to write the native code for Runtime.exec().
I could've sworn that was done.
>Fix javadoc comments in current tree (read some classes don't have
>any).
That's a no no. Somebody better start writing documentation!
--
Aaron M. Renn ([EMAIL PROTECTED]) http://www.urbanophile.com/arenn/
