Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/3405#issuecomment-64115070
Yeah, I'm not clear why only this module is treating javadoc warnings as
errors. Ideally we'd figure that out too. But strictly speaking it's just
necessary to figure out how to not make javadoc for these classes now, but I
don't know how yet. I don't think we should have to fill in all that javadoc in
general; it's too much work. This shouldn't be required. But was just
suggesting that it _is_ a way to workaround this in the short term too!
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
