This is an automated email from the ASF dual-hosted git repository. ascheman pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/maven-site.git
commit 53d9b5c46a9ef2515dfd2ba0d15d0a948b54668b Author: Gerd Aschemann <[email protected]> AuthorDate: Wed Jun 17 18:53:27 2026 +0200 [#12288] Doc <activation> limit on resolver props The aether.* properties declared in 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 (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 <activation> 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. --- content/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 ef08d009..49eb5410 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. </profiles> ``` +**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, `<activeByDefault>true</activeByDefault>` does **not** suffice -- the resolver session is built before profile activation conditions are evaluated. List the profile id under `<activeProfiles>` (or pass `-P <id>`) 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 2abadec7..6b5ed34c 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` </settings> ``` -**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 <id>`. Profiles activated through `<activation>` conditions in the profile itself (`<activeByDefault>`, `<jdk>`, `<os>`, `<property>`, `<file>`) 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`
