[JENKINS-41631] Deleting the Maven Embedder dependency from the test harness #62
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.
Critical for JENKINS-41631 since some of the harder problems relate to random libraries pulled in via the
lib-jenkins-maven-embedder
dependency.Taking a closer look at the harness code using this library, I could not find any realistic cases where it would actually be used. We already look up test dependencies from the classpath. Furthermore, the group IDs covered are old Hudson names no longer used by Jenkins.
@reviewbybees