Skip to content

Add post: The Dependency Your Build Downloads That No Maven Tool Will Show You - #100

Open
algomaster99 wants to merge 1 commit into
mainfrom
claude/maven-hermetic-builds-blog-post
Open

Add post: The Dependency Your Build Downloads That No Maven Tool Will Show You#100
algomaster99 wants to merge 1 commit into
mainfrom
claude/maven-hermetic-builds-blog-post

Conversation

@algomaster99

Copy link
Copy Markdown
Member

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, or go-offline — and where go-offline's own populated repo fails an mvn --offline test. Also touches on the same pattern in Failsafe, maven-compiler-plugin's annotationProcessorPaths (MCOMPILER-503), Quarkus deployment JARs, and protobuf-maven-plugin + os-maven-plugin, then explains how maven-lockfile's in-progress DynamicResolutionSpy extension (chains-project/maven-lockfile#1623) closes the gap for generate/freeze.

Added to the "Posts" list on the index page, newest first.

Test plan

  • Rendered locally as markdown; frontmatter matches existing posts (ai-bump.md, agentic-supply-chain-security.md)
  • Links checked: issue/PR references point at real, currently-open chains-project/maven-lockfile items

Generated by Claude Code

… 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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants