You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "harshab054 (via GitHub)" <gi...@apache.org> on 2026/09/24 17:49:14 UTC
[PR] Mng 8752 provided transitive [maven]
harshab054 opened a new pull request, #13267:
URL: https://github.com/apache/maven/pull/13267
<!--
Please open pull requests against one of the following branches:
- master — default target for all changes (new features + bug fixes).
If the change should also go to maven-4.0.x, request a backport in the PR.
- maven-3.10.x — target for 3.x changes (new features + bug fixes).
If the change should also go to maven-3.9.x, request a backport in the PR.
maven-3.9.x should receive only serious bug fixes, as it is approaching EOL.
Backports are typically handled by maintainers;
however, after agreement you may open a separate backport PR to the target maintenance branch.
-->
Following this checklist to help us incorporate your
contribution quickly and easily:
- [ ] Your pull request should address just one issue, without pulling in other changes.
- [ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
- [ ] Each commit in the pull request should have a meaningful subject line and body.
Note that commits might be squashed by a maintainer on merge.
- [ ] Write unit tests that match behavioral changes, where the tests fail if the changes to the runtime are not applied.
This may not always be possible but is a best-practice.
- [ ] Run `mvn verify` to make sure basic checks pass.
A more thorough check will be performed on your pull request automatically.
- [ ] You have run the [Core IT][core-its] successfully.
If your pull request is about ~20 lines of code you don't need to sign an
[Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf) if you are unsure
please ask on the developers list.
To make clear that you license your contribution under
the [Apache License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0)
you have to acknowledge this by using the following check-box.
- [ ] I hereby declare this contribution to be licenced under the [Apache License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0)
- [ ] In any other case, please file an [Apache Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf).
[core-its]: https://maven.apache.org/core-its/core-it-suite/
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@maven.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] Mng 8752 provided transitive [maven]
Posted by "gnodet-bot (via GitHub)" <gi...@apache.org>.
gnodet-bot commented on code in PR #13267:
URL: https://github.com/apache/maven/pull/13267#discussion_r4119062251
##########
api/maven-api-core/src/main/java/org/apache/maven/api/DependencyScope.java:
##########
@@ -73,6 +73,21 @@ public enum DependencyScope {
/**
* Provided.
+ * <p>
+ * A dependency required for compilation and testing that is expected to be provided at runtime
+ * by the JDK or the runtime environment/container.
+ * <p>
+ * <b>Transitivity and classpath behavior:</b>
+ * <ul>
+ * <li><b>Downstream transitivity:</b> Dependencies in this scope are not transitive to projects
+ * that depend on this project.</li>
+ * <li><b>Upstream transitivity:</b> Transitive {@code compile} and {@code runtime} dependencies
+ * of a provided dependency are included and assigned effective {@code provided} scope.</li>
+ * <li><b>Omitted dependencies:</b> Transitive {@code provided} and {@code test} dependencies of
+ * a provided dependency are omitted.</li>
Review Comment:
💡 **Javadoc style nit:** The `<p>` tags here use the "bare paragraph separator" style (just `<p>` on its own line). While valid, the Maven codebase's Checkstyle configuration may flag this. Verify it passes `mvn checkstyle:check` on this module.
Also, the other scope constants in this enum use minimal one-line Javadoc (e.g., `COMPILE` = `Compile, runtime and test.`). Consider filing a follow-up issue to bring the other scopes up to the same documentation level as `PROVIDED` here — or do it in this PR to avoid inconsistency.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@maven.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org