RFR: 8152818: Javadoc must support module options supported by javac.

[Jonathan Gibbons]

On 04/07/2016 10:04 PM, Martin Buchholz wrote:
> I'm not really qualified, but here are random comments:
>
> I think the general idea is right - javac and javadoc need the same
> kind of support for modules.
> I worry that details may be different, e.g. javadoc has diamond
> inheritance and pulls in via @{inheritDoc} part of the
> "implementation" from module sources.

Can you explain this a bit more?   Is this a new problem in JDK 9, 
with/without modules, or
is it a pre-existing problem with @inheritDoc ?

>
> It would be nice if there was a working sample javadoc command line
> for jsr166 CVS.

What would you want to be the goal of such a command line?  Would it be 
to just
document the jsr166 classes, or would you want to generate the JavaSE docs
including the latest jsr166 sources?


>
> add SPC before L
> +\  -limitmods <module>(,<module>)* Limit the universe of observable modules\n\
>
>
>
>
> On Thu, Apr 7, 2016 at 6:19 PM, Kumar Srinivasan
> <kumar.x.srinivasan at oracle.com> wrote:
>> Hi,
>>
>> Please review the webrev [1] which fixes [2]. The central theme is, to
>> dispatch
>> all javac related options, off to javac's argument processing, so that it is
>> future
>> proofed and the arguments are processed correctly as required by javac.
>>
>> Thanks
>> Kumar
>>
>> [1] http://cr.openjdk.java.net/~ksrini/8152818/webrev.00/
>> [2] https://bugs.openjdk.java.net/browse/JDK-8152818