-
Enhancement
-
Resolution: Won't Fix
-
P4
-
None
-
1.2.0
-
sparc
-
solaris_2.6
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-2029991 | 5.0 | Douglas Kramer | P4 | Closed | Won't Fix |
When you implement incremental builds of javadoc (probably in XML),
I'd like to see the intermediate javadoc files bound into a jar files with
their corresponding .class files. For instance, for the Java Platform classes,
there would be two versions of rt.jar:
- one with the .class files and the intermediate (XML) javadoc files
- a second version with just the .class files
This way a developer that wants to create javadocs could easily include
links to all the java.lang , etc. class javadocs without having to
download all of the source files. Thus, I'd be able to run javadoc on
my code (with -classpath for any needed jar files) and the resulting
HTML would include information about the jar's .class files.
It would also be great if the jar command supported the inclusion of
intermediate javadoc files into the jar file. This would help developers
who want to provide javadoc-able information without including source files.
This would also keep the documentation in sync with the .class files. So...
there would be no question which set of source files (e.g., the old
source.zip) or which set of linked in HTML files went with the classes in
the current set of jar files.
I'd like to see the intermediate javadoc files bound into a jar files with
their corresponding .class files. For instance, for the Java Platform classes,
there would be two versions of rt.jar:
- one with the .class files and the intermediate (XML) javadoc files
- a second version with just the .class files
This way a developer that wants to create javadocs could easily include
links to all the java.lang , etc. class javadocs without having to
download all of the source files. Thus, I'd be able to run javadoc on
my code (with -classpath for any needed jar files) and the resulting
HTML would include information about the jar's .class files.
It would also be great if the jar command supported the inclusion of
intermediate javadoc files into the jar file. This would help developers
who want to provide javadoc-able information without including source files.
This would also keep the documentation in sync with the .class files. So...
there would be no question which set of source files (e.g., the old
source.zip) or which set of linked in HTML files went with the classes in
the current set of jar files.
- backported by
-
JDK-2029991 supplemental: Include intermed. javadoc files with .class files in separate .jar
-
- Closed
-