(I'm running out of puns for post titles - suggestions in the comments please! ;) )

I've put very preliminary CVS Japi results between Classpath's generics branch and JDK1.5 up. Thanks to Andrew, these will be regenerated every night using the very latest japitools.

There are an awful lot of known bugs and limitations right now. If you intend to use these results for anything, I strongly suggest being very careful to confirm by other means that there really is a problem before wasting any time trying to fix it.

If anyone's looking for an easy way to contribute to Japitools, one thing that would be extremely handy would be a regression test system. Given a .java file, compile it, Japize the result and confirm that it's equal to the expected result (apart from the timestamp etc). Or, given two .java files, compile them both, Japize them both, japicompat them, and confirm that the expected errors show up. As everyone knows, code without regression tests is just asking for things to break and nobody to notice.

Sven tackled the last 1.2 Font issue, but the BeanContext one turned out to be, quite literally, one step forward and two steps back. Fixing the Japi bug that had led to an incorrect SVUID revealed that two other classes in the same package had trusted the old Japi information, so now they're wrong instead. So still 9 errors total...