-
Notifications
You must be signed in to change notification settings - Fork 9.2k
HADOOP-19608. Upgrade to JUnit 5.13.3 + Surefire 3.5.3 #7785
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from 2 commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -187,9 +187,18 @@ | |
| </extraJavaTestArgs> | ||
| <!-- Plugin versions and config --> | ||
| <maven-surefire-plugin.argLine>-Xmx4096m -Xss2m -XX:+HeapDumpOnOutOfMemoryError ${extraJavaTestArgs}</maven-surefire-plugin.argLine> | ||
| <maven-surefire-plugin.version>3.0.0-M4</maven-surefire-plugin.version> | ||
| <maven-surefire-plugin.version>3.5.3</maven-surefire-plugin.version> | ||
| <maven-surefire-report-plugin.version>${maven-surefire-plugin.version}</maven-surefire-report-plugin.version> | ||
| <maven-failsafe-plugin.version>${maven-surefire-plugin.version}</maven-failsafe-plugin.version> | ||
| <!-- | ||
| Surefire option to not fail a build if -Dtest=NAME doesn't find a | ||
| test called NAME. This is needed when running integration tests through | ||
| failsafe, as setting -Dtest=none is the way to stop surefire | ||
| running all unit tests before the it.test option is picked up. | ||
| --> | ||
| <surefire.failIfNoSpecifiedTests>false</surefire.failIfNoSpecifiedTests> | ||
| <!-- Flag to stop surefire from shortening test stacks --> | ||
| <trimStackTrace>false</trimStackTrace> | ||
|
|
||
| <maven-clean-plugin.version>3.1.0</maven-clean-plugin.version> | ||
| <maven-install-plugin.version>2.5.1</maven-install-plugin.version> | ||
|
|
@@ -225,9 +234,9 @@ | |
| <sshd.version>2.11.0</sshd.version> | ||
| <hbase.version>2.6.1-hadoop3</hbase.version> | ||
| <junit.version>4.13.2</junit.version> | ||
| <junit.jupiter.version>5.8.2</junit.jupiter.version> | ||
| <junit.vintage.version>5.8.2</junit.vintage.version> | ||
| <junit.platform.version>1.8.2</junit.platform.version> | ||
| <junit.jupiter.version>5.13.3</junit.jupiter.version> | ||
| <junit.vintage.version>5.13.3</junit.vintage.version> | ||
| <junit.platform.version>1.13.3</junit.platform.version> | ||
| <assertj.version>3.12.2</assertj.version> | ||
| <jline.version>3.9.0</jline.version> | ||
| <powermock.version>2.0.9</powermock.version> | ||
|
|
@@ -1315,11 +1324,6 @@ | |
| <artifactId>mockito-all</artifactId> | ||
| <version>1.10.19</version> | ||
| </dependency> | ||
| <dependency> | ||
| <groupId>org.mockito</groupId> | ||
| <artifactId>mockito-junit-jupiter</artifactId> | ||
| <version>3.12.4</version> | ||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. is this change necessary? or just clean up unused dependency declarations
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I was getting a warning of a double reference, and while I was doing jupiter stuff, thought I should do this too |
||
| </dependency> | ||
| <dependency> | ||
| <groupId>org.objenesis</groupId> | ||
| <artifactId>objenesis</artifactId> | ||
|
|
@@ -2498,7 +2502,6 @@ | |
| <DYLD_LIBRARY_PATH>${env.DYLD_LIBRARY_PATH}:${project.build.directory}/native/target/usr/local/lib:${hadoop.common.build.dir}/native/target/usr/local/lib</DYLD_LIBRARY_PATH> | ||
| <MALLOC_ARENA_MAX>4</MALLOC_ARENA_MAX> | ||
| </environmentVariables> | ||
| <trimStackTrace>false</trimStackTrace> | ||
| <systemPropertyVariables> | ||
|
|
||
| <hadoop.log.dir>${project.build.directory}/log</hadoop.log.dir> | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i think this is some leftover? if so, do drop it before you commit
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yeah, I missed that, and yes, its to be dropped. It'll force hadoop-common tests to run as the final safety check