fix: not finding sources in non-standard directories #3260
Merged
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.
In Maven POM, the standard directory layout for sources and test sources can be overridden from the standard
src/main/java
andsrc/test/java
as follows:The description for the field
sourceDirectory
states:Previously, when using MavenLauncher, if this value is defined it will be used instead of the standard directory structure when searching for sources. The issue is that this relative path is not prefixed with the absolute path to the project directory. This means that it assumes the current working directory, which is not necessarily the path to the Maven project being analysed.
PR contains previously failing test case with suggested fix.