move maven-javadoc-plugin to <build> #7
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
|
@XenoAmess |
XenoAmess
force-pushed
the
add_javadoc_to_build
branch
from
bdfb171
to
4aa2c36
Compare
@garydgregory rebase/test done. |
|
I'm not convinced Javadoc should be dropped from the reporting section. |
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.
move maven-javadoc-plugin from
<report>to<build>.As quite some of (if not most of) commons projects have javadoc error, minor ones or major ones.
I think it is better to let people know if they makes javadoc uncorrectly when they create/change javadoc, but not when release.