On Thu, 2004-09-30 at 11:56, Stuart Ballard wrote: > Michael Koch wrote: > > Its possible again afaik. Another option would be to make it its own > > CVS module in classpath or cp-tools. > > I won't object if this is the consensus of others, but my own preference > is to keep japitools as a separate project. It isn't only useful for > Classpath or classpath-using projects - it can be used to compare > independent implementations of *any* API. For example, any of the > "standard extensions" that Sun develops that aren't part of the core > Java platform. The developers of various J2EE components might be > interested too, for example. > > Since it does, indeed, seem like Savannah is accepting new registrations > again, I've put in one for japitools.
Stuart, I've taken the serialization tests I once gave you to add to japitools and added those to a module in Mauve called 'serialization'. A new Mauve module seems like a good home for the japitools project to me, but it's up to you... and Tom too. Brian -- Brian Jones <[EMAIL PROTECTED]>
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Classpath mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/classpath
