Nathan Beyer wrote:
That's what I've been using, so I would say it's a fairly good place to
start. The other technique I use in conjunction is generating the javadoc
from the Harmony source. This allows for some noticing some of the larger
holes when visually comparing it to the specification.
The other piece that might be interesting is running one of those tools that
scans for TODO and FIXME comments and reports the what and where.
I thought IDEA and Eclipse do this....
geir
-Nathan
-----Original Message-----
From: Geir Magnusson Jr [mailto:[EMAIL PROTECTED]
Sent: Thursday, May 25, 2006 6:57 AM
To: harmony-dev@incubator.apache.org
Subject: [classlib] JAPI data to drive packages to completion
I was staring at the JAPI data last night. Can anyone think of a reason
why we wouldn't suggest to people looking for something to do to use
JAPI reports to help finish packages?
geir
---------------------------------------------------------------------
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
