-
Notifications
You must be signed in to change notification settings - Fork 467
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error building javadocs #18
Labels
Milestone
Comments
This only seems to happen with Java 8. Thanks for reporting. We will address this in a future release. |
pfifer
added a commit
to pfifer/amazon-kinesis-client
that referenced
this issue
Feb 27, 2017
* Fixed an issue building JavaDoc for Java 8. * [Issue awslabs#18](awslabs#18) * [PR awslabs#141](awslabs#141) * Reduce Throttling Messages to WARN, unless throttling occurs 6 times consecutively. * [Issue awslabs#4](awslabs#4) * [PR awslabs#140](awslabs#140) * Fixed two bugs occurring in requestShutdown. * Fixed a bug that prevented the worker from shutting down, via requestShutdown, when no leases were held. * [Issue awslabs#128](awslabs#128) * Fixed a bug that could trigger a NullPointerException if leases changed during requestShutdown. * [Issue awslabs#129](awslabs#129) * [PR awslabs#139](awslabs#139) * Upgraded the AWS SDK Version to 1.11.91 * [PR awslabs#138](awslabs#138) * Use an executor returned from `ExecutorService.newFixedThreadPool` instead of constructing it by hand. * [PR awslabs#135](awslabs#135) * Correctly initialize DynamoDB client, when endpoint is explicitly set. * [PR awslabs#142](awslabs#142)
pfifer
added a commit
that referenced
this issue
Feb 27, 2017
* Fixed an issue building JavaDoc for Java 8. * [Issue #18](#18) * [PR #141](#141) * Reduce Throttling Messages to WARN, unless throttling occurs 6 times consecutively. * [Issue #4](#4) * [PR #140](#140) * Fixed two bugs occurring in requestShutdown. * Fixed a bug that prevented the worker from shutting down, via requestShutdown, when no leases were held. * [Issue #128](#128) * Fixed a bug that could trigger a NullPointerException if leases changed during requestShutdown. * [Issue #129](#129) * [PR #139](#139) * Upgraded the AWS SDK Version to 1.11.91 * [PR #138](#138) * Use an executor returned from `ExecutorService.newFixedThreadPool` instead of constructing it by hand. * [PR #135](#135) * Correctly initialize DynamoDB client, when endpoint is explicitly set. * [PR #142](#142)
This should now be fixed in the current release. Please reopen if you're still having an issue. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The text was updated successfully, but these errors were encountered: