Clarify consumer POM behavior regarding dependency scopes - #1606
Open
gnodet wants to merge 1 commit into
Open
Conversation
Restructure the Consumer POM section to distinguish default behavior (preserves all dependency scopes including provided) from flattened behavior (strips non-transitive scopes). Add a clarifying note to the build/consumer POM comparison table. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
elharo
requested changes
Aug 9, 2026
| Only build-time-only elements are stripped. | ||
|
|
||
| * It contains no parent POM references (all inherited elements are resolved and included directly) | ||
| Optionally, flattening can be enabled to produce a fully self-contained consumer POM. When flattening is enabled: |
Contributor
There was a problem hiding this comment.
Optionally, flattening can be enabled to produce a fully self-contained consumer POM. --> Enable flattening to produce a fully self-contained consumer POM.
| * It contains no parent POM references (all inherited elements are resolved and included directly) | ||
| Optionally, flattening can be enabled to produce a fully self-contained consumer POM. When flattening is enabled: | ||
|
|
||
| * Parent POM references are resolved (all inherited elements are included directly) |
Contributor
There was a problem hiding this comment.
Try to avoid parenthesized expressions
| * Parent POM references are resolved (all inherited elements are included directly) | ||
| * BOM imports are flattened into the dependency list | ||
| * Only transitive dependencies are kept (compile and runtime scopes) | ||
| * Only transitive dependencies are kept (`compile` and `runtime` scopes); non-transitive scopes (`provided`, `test`, `system`) are stripped |
Contributor
There was a problem hiding this comment.
Transitive dependencies are kept (compile and runtime scopes). Non-transitive scopes are stripped. (provided, test, system scopes)
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
provided) from flattened behavior (strips non-transitive scopes likeprovided,test,system)buildclassifier when flattening is enabledRefs #11442
Test plan
mvn site🤖 Generated with Claude Code