Make generating javadoc jars optional #620
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
Occasionally generating javadoc jars is more complicated than compiling the raw source code (eg. when documenting code that uses Lombok) Rather than make people jump hoops to generate the javadoc jar (which may not actually be used) add a new tag we check for: `no-javadocs`
cheister
approved these changes
Nov 18, 2021
jin
approved these changes
Nov 19, 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.
Occasionally generating javadoc jars is more complicated than
compiling the raw source code (eg. when documenting code that uses
Lombok) Rather than make people jump hoops to generate the javadoc jar
(which may not actually be used) add a new tag we check for:
no-javadocs