Skip to content

[#12288] Doc: <activation> limit on resolver-config profiles #1602

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ascheman merged 2 commits into from
Jul 18, 2026
Merged

[#12288] Doc: <activation> limit on resolver-config profiles #1602

Show file tree
Hide file tree
Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
0874f09
[#12288] Doc <activation> limit on resolver props
ascheman Jun 17, 2026
b01f578
[#12288] Address Copilot review: fix typo + split NOTICE for readability
Jun 23, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions content/markdown/guides/introduction/introduction-to-profiles.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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`:
Expand Down
3 changes: 1 addition & 2 deletions content/markdown/guides/mini/guide-resolver-transport.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Comment thread
ascheman marked this conversation as resolved.
Outdated

You can also use environment variable `MAVEN_OPTS` ot `MAVEN_ARGS`

@ascheman ascheman Jun 23, 2026

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed in b01f578 — 'ot' -> 'or'.


Expand Down