Need sponsor to fix Javadoc warnings

Vipin Sharma vipinsharma85 at gmail.com
Wed Apr 8 16:35:34 UTC 2020



> On Apr 8, 2020, at 6:57 PM, Pavel Rappo <pavel.rappo at oracle.com> wrote:
> 
> Why assume something that sophisticated where it can be adequately explained by
> a simpler thing? :) I bet it was an IDE inspection.
> 
> -Pavel

Yes, it was IDE inspection in java.base, it looked like the best way to start contributing and understand the process.
If it helps and not creating noise for you all, I see an opportunity for one more such patch. What do you think?

> 
>> On 8 Apr 2020, at 14:14, Alan Bateman <Alan.Bateman at oracle.com> wrote:
>> 
>> On 08/04/2020 14:07, Daniel Fuchs wrote:
>>> Hi Pavel,
>>> 
>>> On 08/04/2020 13:56, David Holmes wrote:
>>>> and `@exception` tags for checked exceptions that were neither thrown
>>>> nor imported
>>> 
>>> Hopefully that's only on internal classes.
>> From a quick scan, the changes are to internal classes and a few non-public elements of public API classes. So I don't think anything should impact the javadoc. I'm guessing this patch is motivated by something creating that is running the javadoc tool with different options to what the "docs" target uses.
>> 
>> -Alan
> 

Regards,
Vipin


More information about the security-dev mailing list