8035473: [javadoc] Revamp the existing Doclet APIs

Magnus Ihse Bursie magnus.ihse.bursie at oracle.com
Tue Jan 26 10:47:07 UTC 2016

On 2016-01-26 08:49, Jonathan Gibbons wrote:
> On 01/25/2016 06:20 AM, Magnus Ihse Bursie wrote:
>> On 2016-01-23 00:49, Jonathan Gibbons wrote:
>>> On 01/22/2016 03:41 PM, Magnus Ihse Bursie wrote:
>>>> In make/Javadoc.gmk:
>>>> What's the story with all these old doclet duplication? 
>>> The story is that we're adding a completely new public API, and 
>>> there are existing users of the existing API, both good and bad. The 
>>> good ones are just using the Doclet API itself (and providing their 
>>> own doclet), the bad ones are using and overriding classes in the 
>>> (internal) implementation of the standard doclet.  Since we have not 
>>> hitherto given notice about anything going away, for the time being 
>>> we'll keep old and new side by side.
>> And we still have users of the old API internally in the JDK? Are the 
>> plan for them to go away in a JDK 10 frame as well, or will we 
>> convert all the old one's to the new format in JDK 9, so the current 
>> duplication in Javadoc.gmk is only temporary?
>> /Magnus
> There are existing usages of the old doclet API that will not be 
> converted before we ship JDK 9, so the old and new code will need to 
> exist side by side at least through the lifetime of JDK 9, while we 
> decide how and when to retire the old code.
Ok, I see.

Then I'm satisfied with the review from a build perspective.


> -- Jon

More information about the build-dev mailing list