Follow-up #6572: Re-order test classpath to load correct Logger as workaround for KT-60813 #6636
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.
This solution replaces the slf4j Logger with the correct one by classpath ordering: c4ef737
I ran into #4140/#4170 not being implemented fully (current implementation is based on assumptions). The assumption is that the
/
resource on the classpath points to the current module's test sourceSet. By changing the order I changed this and now the slf4j.jar is on the classpath first, which triggers #4140. I was able to workaround this by looking for a specific file that's in the correct folder (ba150db), but it's not scalable, so I instead changed the logic to insert the new dependency in the middle of the classpath: 68352ce