> -Original Message-
> From: Geir Magnusson Jr [mailto:[EMAIL PROTECTED]
> Sent: Thursday, May 25, 2006 9:49 AM
> To: harmony-dev@incubator.apache.org
> Subject: Re: [classlib] JAPI data to drive packages to completion
> > The other piece that might be interesting is
Mikhail Fursov wrote:
I saw a report generated from JAPI output with percent of package
implementation progress on gnu-classpath related site. We can use the same
statistics in harmony...
Like this: http://www.kaffe.org/~stuart/japi/htmlout/h-jdk14-classpath.html
LOL. Yes, that is what I wa
On 26 May 2006 at 2:05, "Mikhail Fursov" <[EMAIL PROTECTED]> wrote:
>
> I saw a report generated from JAPI output with percent of package
> implementation progress on gnu-classpath related site. We can use the same
> statistics in harmony...
>
> Like this: http://www.kaffe.org/~stuart/japi/htmlo
On 25 May 2006 at 9:01, "Nathan Beyer" <[EMAIL PROTECTED]> wrote:
>
> That's what I've been using, so I would say it's a fairly good place
> to start.
So I'd noticed! ;-)
I've been keeping track of JAPI figures for just the bits of the API for
which we have contributions. Currently (for the 1.5
I saw a report generated from JAPI output with percent of package
implementation progress on gnu-classpath related site. We can use the same
statistics in harmony...
Like this: http://www.kaffe.org/~stuart/japi/htmlout/h-jdk14-classpath.html
On 5/25/06, Geir Magnusson Jr <[EMAIL PROTECTED]> wrot
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.
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 mi
