-
Notifications
You must be signed in to change notification settings - Fork 134
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
JavaDoc uses UTF-8 encoding #1879
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Generate changelog in
|
carterkozak
approved these changes
Aug 15, 2021
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm, thanks!
Released 4.16.0 |
This was referenced Aug 15, 2021
Merged
This was referenced Aug 15, 2021
bulldozer-bot bot
pushed a commit
to palantir/witchcraft-api
that referenced
this pull request
Aug 17, 2021
###### _excavator_ is a bot for automating changes across repositories. Changes produced by the roomba/latest-baseline-oss check. # Release Notes ## 4.14.0 _Automated release, no documented user facing changes_ ## 4.15.0 | Type | Description | Link | | ---- | ----------- | ---- | | Improvement | Automatically fix upstream `LoopOverCharArray` | palantir/gradle-baseline#1873 | ## 4.16.0 | Type | Description | Link | | ---- | ----------- | ---- | | Improvement | JavaDoc uses UTF-8 encoding by default | palantir/gradle-baseline#1879 | ## 4.17.0 | Type | Description | Link | | ---- | ----------- | ---- | | Improvement | Enforce `PreferSafeLogger` at `WARNING` level matching `Slf4jLogsafeArgs` and `PreferSafeLoggingPreconditions`. This doesn't apply to gradle plugins. | palantir/gradle-baseline#1876 | To enable or disable this check, please contact the maintainers of Excavator.
This was referenced Sep 15, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Before this PR
See palantir/tritium#1192 where JavaDoc is failing to generate on system using default US-ASCII encoding
After this PR
==COMMIT_MSG==
JavaDoc uses UTF-8 encoding by default
==COMMIT_MSG==
Possible downsides?