Add post: The Dependency Your Build Downloads That No Maven Tool Will Show You - #100
Merged
Merged
Conversation
… Show You Covers the Surefire+JUnit5 dynamic-provider-resolution case (also affecting Failsafe, maven-compiler-plugin's annotationProcessorPaths, Quarkus, and protobuf-maven-plugin+os-maven-plugin): why dependency:tree, resolve-plugins, go-offline, and trusted checksums are all structurally blind to artifacts a plugin resolves imperatively at execution time, and how maven-lockfile's in-progress DynamicResolutionSpy extension closes that gap for generate/freeze.
algomaster99
marked this pull request as draft
August 11, 2026 12:50
The parent POM org.apache.maven.surefire:surefire-providers:3.2.5 was missing from the original count - it's needed to resolve surefire-junit-platform's effective model (and is where the unversioned junit-platform-launcher dependency gets pinned to 1.9.3), but is only ever reachable through the same dynamic root, so it's equally invisible to static tools. Also clarifies that junit-platform-launcher resolves to two different versions (1.9.3 via the POM chain, 1.10.2 preferred by Surefire's own classpath assembly at runtime), and adds an ASCII diagram showing the actual parent-POM/dependency edges.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Summary
New post walking through the Surefire + JUnit 5 dynamic-resolution case (chains-project/maven-lockfile#1568): a minimal repro where Surefire resolves its test-framework provider imperatively at execution time, producing 7 artifacts that appear in none of
dependency:tree,resolve-plugins, orgo-offline— and wherego-offline's own populated repo fails anmvn --offline test. Also touches on the same pattern in Failsafe,maven-compiler-plugin'sannotationProcessorPaths(MCOMPILER-503), Quarkus deployment JARs, and protobuf-maven-plugin + os-maven-plugin, then explains how maven-lockfile's in-progressDynamicResolutionSpyextension (chains-project/maven-lockfile#1623) closes the gap forgenerate/freeze.Added to the "Posts" list on the index page, newest first.
Test plan
ai-bump.md,agentic-supply-chain-security.md)Generated by Claude Code