Introduce Classpath duplicates check test (again) #2311
Closed
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.
[NB: This PR is a copy of #2309 due to #2310; let's see if this works better and passes CI build.]
Related to (and initial version of) #2220.
This introduces a (first) test which discovers, and fails in case of, duplicates in JARs on the classpath.
It already found 1 issue which seems a bit suspicious (to me), see #2308, but for now excludes that.
If this is acceptable, my idea (next step) is to extend this to the other (and more interesting) modules than just common.