ascheman opened a new pull request, #1602: URL: https://github.com/apache/maven-site/pull/1602
> **Status: Draft — waiting on outcomes of [apache/maven#12288](https://github.com/apache/maven/issues/12288)** > > The wording in this PR is accurate for current Maven 3.x and all currently-released Maven 4 RCs, but three open clarifications determine the final shape: > > 1. When the fix from [apache/maven#12297](https://github.com/apache/maven/pull/12297) / [apache/maven#12298](https://github.com/apache/maven/pull/12298) (the `<activeByDefault>` propagation fix for Maven 4) ships — the doc would then qualify the limitation to "Maven 4 before X.Y, and all Maven 3.x". > 2. Whether a backport to Maven 3.9.x is accepted (asked at [#12288](https://github.com/apache/maven/issues/12288)). > 3. Whether a runtime `[WARNING]` is added for the remaining four activation conditions (`<jdk>`, `<os>`, `<property>`, `<file>`) — also asked at [#12288](https://github.com/apache/maven/issues/12288). > > Will flip to Ready for Review once those three are settled and the wording is refreshed accordingly. ## What this PR does Two doc clarifications around the long-standing limitation that `aether.*` properties declared inside a `settings.xml` profile only take effect if the profile is listed under `<activeProfiles>` or activated via CLI `-P`. The limitation has been documented since [MNG-7850](https://issues.apache.org/jira/browse/MNG-7850) (2023, by @slawekjaranowski) but only in the resolver-transport mini-guide; profile-side users would never find it. * `guides/mini/guide-resolver-transport.md` — strengthen the NOTICE so it enumerates what the limitation actually covers (all `<activation>` conditions, not just `activeByDefault`) and gives a one-line rationale. * `guides/introduction/introduction-to-profiles.md` — add a single sentence in the "Active by default" section linking to the mini-guide caveat, so users planning to use `<activeByDefault>` for `aether.*` config are warned where they actually look. ## Versions affected (as currently drafted) Maven 3.x and all currently-released Maven 4 RCs. May need a version-specific qualifier once the fix in #12297 / #12298 ships and the backport question is settled. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
