Fixed JavaDoc errors and warnings #24
Merged
Conversation
This file contains hidden or 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
- Window title as it appears in a browser tab changed to "WorldWindJava API". - JavaDoc document title on overview page changed to "NASA WorldWind Java-Community Edition" - JavaDoc headers at top of docs changed to "NASA WorldWind-CE" - Previous values were "NASA WorldWind" for all.
wcmatthysen
approved these changes
Apr 13, 2019
Member
wcmatthysen
left a comment
wcmatthysen
left a comment
There was a problem hiding this comment.
Nice, I scanned the javadoc fixes that you made and it looks good. It is basically the same what I had in mind.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Description of the Change
Changed the javadoc text to produce an error and warning free build of the community edition WorldWindJava API documentation. Also changed the API documentation branding to reflect the community edition.
Online API branding:
Why Should This Be In Core?
Part of an error free build.
Benefits
Potential Drawbacks
None
Applicable Issues
Closes #16