From 0874f09d4e8d9303a829138252ccbeb08e2797fe Mon Sep 17 00:00:00 2001 From: Gerd Aschemann Date: Wed, 17 Jun 2026 18:53:27 +0200 Subject: [PATCH 1/2] [#12288] Doc limit on resolver props The aether.* properties declared in a settings.xml only take effect if the profile is listed under or activated via CLI -P. The limitation has been documented since MNG-7850 (2023), but only in the resolver-transport mini-guide -- users coming from the profile side never find it. * mini/guide-resolver-transport.md -- strengthen the NOTICE to enumerate all conditions affected (not just activeByDefault) and spell out the timing reason in one sentence. * introduction/introduction-to-profiles.md -- add a Note for resolver configuration sentence in the Active by default section, with cross-link to the mini-guide caveat. Wording is accurate for current Maven 3.x and Maven 4 RCs. apache/maven#12297 fixes the activeByDefault case on Maven 4 master; once that release ships and the backport question is settled, this doc should be updated to qualify the limitation to specific version ranges. --- .../markdown/guides/introduction/introduction-to-profiles.md | 2 ++ content/markdown/guides/mini/guide-resolver-transport.md | 3 +-- 2 files changed, 3 insertions(+), 2 deletions(-) diff --git a/content/markdown/guides/introduction/introduction-to-profiles.md b/content/markdown/guides/introduction/introduction-to-profiles.md index ef08d00979..49eb5410c9 100644 --- a/content/markdown/guides/introduction/introduction-to-profiles.md +++ b/content/markdown/guides/introduction/introduction-to-profiles.md @@ -126,6 +126,8 @@ Example to set a profile active by default. ``` +**Note for resolver configuration:** When configuring [Maven Resolver](../mini/guide-resolver-transport.html#system-level) low-level options (`aether.*` system properties) in a `settings.xml` profile, `true` does **not** suffice -- the resolver session is built before profile activation conditions are evaluated. List the profile id under `` (or pass `-P `) instead. + ##### JDK The following configuration will trigger the profile when the JDK's version _starts with_ `1.4` (for example `1.4.0_08`, `1.4.2_07`, `1.4`), in particular it _won't be active_ for **newer** versions like `1.8` or `11`: diff --git a/content/markdown/guides/mini/guide-resolver-transport.md b/content/markdown/guides/mini/guide-resolver-transport.md index 2abadec7e1..6b5ed34ca3 100644 --- a/content/markdown/guides/mini/guide-resolver-transport.md +++ b/content/markdown/guides/mini/guide-resolver-transport.md @@ -148,8 +148,7 @@ Configuration can be provided on global level as properties in `settings.xml` ``` -**NOTICE** -- only profiles activated by `settings/activeProfiles` will be taken for consideration - you can not use `profile/activation` in such case +**NOTICE:** Only profiles activated by `settings/activeProfiles` (the explicit list at the bottom of `settings.xml`) are honored here, or by CLI `-P `. Profiles activated through `` conditions in the profile itself (``, ``, ``, ``, ``) are **not** taken into account for the resolver session config -- the resolver session is built before Maven evaluates those conditions. You can also use environment variable `MAVEN_OPTS` ot `MAVEN_ARGS` From b01f578a5a8eacc43f0a5e16fbcfbf0e3320efc3 Mon Sep 17 00:00:00 2001 From: Gerd Aschemann Date: Tue, 23 Jun 2026 16:31:44 +0200 Subject: [PATCH 2/2] [#12288] Address Copilot review: fix typo + split NOTICE for readability * Fix typo on line 153: 'ot' -> 'or'. * Split the long single-sentence NOTICE into a two-bullet list of the honored activation channels plus a separate sentence on rationale, per Copilot suggestion at line 151. --- content/markdown/guides/mini/guide-resolver-transport.md | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/content/markdown/guides/mini/guide-resolver-transport.md b/content/markdown/guides/mini/guide-resolver-transport.md index 6b5ed34ca3..409e462075 100644 --- a/content/markdown/guides/mini/guide-resolver-transport.md +++ b/content/markdown/guides/mini/guide-resolver-transport.md @@ -148,9 +148,14 @@ Configuration can be provided on global level as properties in `settings.xml` ``` -**NOTICE:** Only profiles activated by `settings/activeProfiles` (the explicit list at the bottom of `settings.xml`) are honored here, or by CLI `-P `. Profiles activated through `` conditions in the profile itself (``, ``, ``, ``, ``) are **not** taken into account for the resolver session config -- the resolver session is built before Maven evaluates those conditions. +**NOTICE:** Only profiles activated explicitly are honored here: -You can also use environment variable `MAVEN_OPTS` ot `MAVEN_ARGS` +* via `` (the explicit list at the bottom of `settings.xml`), or +* via CLI `-P `. + +Profiles activated through `` conditions in the profile itself — ``, ``, ``, ``, `` — are **not** taken into account for the resolver session config: the resolver session is built before Maven evaluates those conditions. + +You can also use environment variable `MAVEN_OPTS` or `MAVEN_ARGS` ``` export MAVEN_ARGS="-Daether.connector.http.preemptiveAuth=true"