[
https://issues.apache.org/jira/browse/LUCENE-875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12494786
]
Doron Cohen commented on LUCENE-875:
------------------------------------
Also, since failOnEror was added to the javadocs task, build services (e.g.
parabuild) with jars misconfigured would fail not only because of javadoc
warnings but also because of javadoc errors.
I feel that the noise this created with the failures of builds due to javadocs
problems is a price to high to pay for being automatically "forced" to keep
javadocs error/warning free. I am disabling both fail-on-jdoc-error and
fail-on-jdoc-warning.
I will add an item "check javadocs creation" to Wiki's "Patch Check List" page.
> javadocs creation has too many warnings/errors
> ----------------------------------------------
>
> Key: LUCENE-875
> URL: https://issues.apache.org/jira/browse/LUCENE-875
> Project: Lucene - Java
> Issue Type: Task
> Components: Javadocs
> Affects Versions: 2.2
> Reporter: Doron Cohen
> Assigned To: Doron Cohen
> Priority: Minor
> Fix For: 2.2
>
> Attachments: 875_javacc_patch.txt, 875_javacc_patch.txt,
> 875_javacc_patch.txt
>
>
> Currently running 'ant javadocs' creates so many warnings that you have to
> grep the output to verify that new code did not add more.
> While most current errors might be minor, they might hide a few serious ones
> that we will never know abut until someone complains.
> Best if we fix all of them and keep it always clean...
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
