bumps maven-javadoc-plugin to latest 3.2.0 #481
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
abelsromero
force-pushed
the
feature/bump-maven-javadoc-plugin-to-latest-3.2.0
branch
from
847addf
to
87f77f0
Compare
abelsromero
deleted the
feature/bump-maven-javadoc-plugin-to-latest-3.2.0
branch
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.
Thank you for opening a pull request and contributing to asciidoctor-maven-plugin!
What kind of change does this PR introduce? (check at least one)
What is the goal of this pull request?
Originally
maven-javadoc-pluginversion configuration, using the version defined in<pluginManagement>.But also upgrades the version to latest v3.2.0.
Are there any alternative ways to implement this?
Given the plugin is used only once, could define it explicitely.
But for consistency I'd rather have all maven plugin version defined togetherd under pluginManagement.
Are there any implications of this pull request? Anything a user must know?
No.
Is it related to an existing issue?
Finally, please add a corresponding entry to CHANGELOG.adoc