Addresses #528 by upgrading testng to 7.3.0 #529
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
viktorklang
force-pushed
the
wip-upgrade-testng-√
branch
2 times, most recently
from
f27805e to
3bd21f5
Compare
Signed-off-by: Viktor Klang <[email protected]>
viktorklang
force-pushed
the
wip-upgrade-testng-√
branch
from
3bd21f5 to
eff217e
Compare
viktorklang
changed the title
|
Upgrading to 7.4.0 seemed to create artifact resolution problems, which is weird since it definitely is on Maven Central, alas upgrading to 7.3.0 should be enough to make sure that jcommander is upgraded appropriately to 1.78: https://github.com/cbeust/testng/blob/7.3.0/build.gradle.kts#L59 |
akarnokd
approved these changes
Mar 6, 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.
Seemed like the lowest resistance path was to upgrade TestNG itself.