Junit windows fix #6
Open
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
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.
On Windows, the JUnit runner fails to correctly set the classpath when using the '-cp' argument, leading to 'ClassDefNotFound' exceptions.
To fix this issue, the JUnit jar has to be run as a typical Java class, i.e. through the Java classpath.
To accomplish this, the classpath is adjusted to look like the following (Using linux separator as an example):
<junit_runner>:<original_classpath>In addition the 'spring-mock' dependency is extracted from the original classpath, and moved to the end. Producing the following:
<junit_runner>:<classpath_without_spring-mock>:<spring-mock>This is then run using:
java -cp <updated_classpath> <junit_runner_class> <junit_runner_args>Note: The JUnit runner main class is assumed to be: 'org.junit.platform.console.ConsoleLauncher'