fix: better resolve test scope for invisible project #697
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
Eskibear
approved these changes
May 14, 2019
yaohaizh
approved these changes
May 14, 2019
Eskibear
approved these changes
May 15, 2019
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.
Resolve #470
Now if the project is a General Java project, which means it's a Java project but is not built by Maven/Gradle, Test Runner will always treat the classpaths as test classpaths.
For Maven projects, the user should use
<testSourceDirectory/>to configure the test source paths.For Gradle projects, the user should use
sourceSetsto configure the test source paths.For Eclipse & Invisible projects, all the source files are treated as testable files
For Default (single file) project, it will be ignored.