Update JCommander coordinates for v2.0 #1290
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
update-jcommander-coordiantes-for-v2.0
branch
from
9022f5b
to
6b23e83
Compare
Only artifact coordinates changed, not the packages.
|
Thank you! |
If it helps, I upgraded a personal project and it did not require any change. It seems they simply changed the organization, the code is compatible. |
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.
Kind of change
Description
What is the goal of this pull request?
Bump JCommander to the latest v2.0.
How does it achieve that?
Update the version and the coordinates.
Are there any alternative ways to implement this?
No.
Are there any implications of this pull request? Anything a user must know?
Only artifact coordinates changed, not the packages.
Issue
If this PR fixes an open issue, please add a line of the form:Release notes
Please add a corresponding entry to the file CHANGELOG.adoc