Handle dependent artifacts that have multiple files #130
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.
Turns out,
ArtifactCollection.artifactFiles
coalesces multiple files associated with the same artifact.This manifests itself when e.g. a subproject dependency has a mix of kotlin and java sources and thus has two class output directories (build/classes/kotlin/main and build/classes/java/main). One of the output directories will be "lost" and won't be "seen" by the Gradle task.