For the Tiger build:

(Justification)

Netbeans is developing a code coverage framework from scratch that is
inferior to the one provided by jcov. More usage by Netbeans and
higher code coverage by testing in the field means fewer bugs in
Java programs written by our customers.

For Netbeans (and other tools developers) to hook into jcov requires
that the outputs of jcov be publicly exposed. The outputs (class
file changes and text generated by jcov tools) need to be stable,
but this should not be a huge problem because jcov has been used
for two or three years now. The internal documentation is clear enough
for external exposure, too.

(End justification)

(Scope)
lines of Java code:
lines of c/c++ code:
Key: Small = < 10K; Medium = < 30K; Large = > 30K

Number of new/modified public packages:

and for each of those packages list:

Name of package: com.sun.tools.javac
New/modified public classes:
New/modified public methods:
New/modified private classes:
New/modified private methods:

Key: eXtraSmall < 10; Small < 50; Medium < 100; Large >100

(End scope)

(Effort)
Has the feature already been implemented? n (New code will be based on the
existing implementation in the old compiler.)

If no -
    Approximately how many engineering weeks will it take?



(End effort)

(Compatability)
Known compatibility issues with the previous SDK:
    Source compatibility issues: n
    If yes explain -

Binary compatibility issues: n
    If yes explain -



(End compatability)

(Risks)

(End risks)

(Product Test Development)

Will there be Product Tests for this feature?

JCov is an internal tool.

If yes who will develop the product tests?

If the feature is being considered as a Release Driver, what
is the approximate date by which the tests will be ready?

(End Product Test Development)

(TCK Test Development)

Will there be conformance tests other than signature tests for this feature?

If yes, who will develop the conformance tests?

If the feature is being considered as a Release Driver, what
is the approximate date by which the tests will be ready?

(End TCK Test Development)

(Java Community Process)

Is the new feature part of the Java Community Process:
If so what is the JSR number:
When did/will the review period start?
Who is the owner of the JSR?

(End Java Community Process)

(Timing)

Approximate dates - January, Feburary etc.

When will a initial design doc be ready?
When will an initial implementation be ready?
When will the feature be complete?

Date of complete draft of specification:
Date when feature will be testable:
Date when feature will be complete:

(End Timing)

(Porting issues)

Are you aware of any issues that may make this feature
difficult to port to, or run on:

Windows 95:
Windows 98:
Windows NT:
Solaris:
Linux:

(End Porting issues)

(Documentation)

Who will be responsbile for writing:

Design doc/javadoc:

(End Documentation)

(L10N)

Will you be adding end user visible messages?

approximate number of visible messages:

(End L10N)
======================================================================