[
https://issues.apache.org/jira/browse/SAMZA-462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Kleppmann updated SAMZA-462:
-----------------------------------
Attachment: SAMZA-462.patch.gz
Attaching the result of running {{bin/generate-javadocs.sh}}. It's a huge patch
(1.7MB uncompressed) so I can't help feeling this is doing it wrong. Do the
javadocs need to be in the git repository? Seems like commit history pollution.
If yes, should we just commit javadoc changes without review? The patch is
really far too big to be reviewable.
> Javadocs update
> ---------------
>
> Key: SAMZA-462
> URL: https://issues.apache.org/jira/browse/SAMZA-462
> Project: Samza
> Issue Type: Task
> Reporter: Martin Kleppmann
> Attachments: SAMZA-462.patch.gz
>
>
> Since SAMZA-259, javadocs are committed to git. On the master branch there
> have been some changes that affect the javadocs, such as SAMZA-437. These
> changes are not reflected in the javadocs currently committed to git.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
