[MNGSITE-418] Clarify transitivity of "provided" depdendencies
- Dominant language
- Java
- Stars
- 123
- Forks
- 301
- Avg merge
- 16h 59m
- Merged PRs (30d)
- 32
Description
**[Elliotte Rusty Harold](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=elharo)** opened **[MNGSITE-418](https://issues.apache.org/jira/browse/MNGSITE-418?redirect=false)** and commented
Per https://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html "This scope is only available on the compilation and test classpath, and is not transitive."
"is not transitive" is ambiguous. For instance, suppose
A --> X_provided
A -> B -> Y_provided -> D
Which dependencies are in the compilation and test classpaths of A? Presumably D is not and X_provided is. However is Y_provided included or not?
---
1 votes, 2 watchers
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the dependency mechanism guide linked in the issue and trace its explanation of provided scope and transitivity. Clarify the documented behavior for the A/B/X/Y/D example, including which dependencies appear on A's compilation and test classpaths, so the meaning of “not transitive” is unambiguous.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100