gnodet opened a new pull request, #1691: URL: https://github.com/apache/maven-site/pull/1691
## Summary Improves the `introduction-to-profiles` guide to accurately document the `activeByDefault` suppression behavior, including the intentional asymmetry between POM and external (`settings.xml`) profiles introduced by the fix in [apache/maven#13254](https://github.com/apache/maven/pull/13254). ## Changes ### "Profiles activated by default" intro section The previous single sentence described POM-only behavior and was technically inaccurate (it said "activated using one of the previously described methods" without distinguishing -P vs condition activation). Now: - Clearly states that any same-POM activation (condition or -P) suppresses POM `activeByDefault` profiles - Adds a **Note** explaining that external profiles in `settings.xml` behave differently and points readers to the subsection ### "Active by default" subsection The previous text said this flag is "only evaluated if no other profile is explicitly activated via command line, `settings.xml` or activated through some other activator" — which was both inaccurate and incomplete. Now replaced with a clear bullet breakdown: - **POM profiles**: suppressed by any same-POM activation (condition or -P) - **External profiles**: suppressed only by explicit -P, with rationale explaining why the asymmetry is intentional (external profiles carry environment config like repos/credentials that shouldn't be wiped out by a JDK-triggered POM profile) ## Related - apache/maven#13254 — the code fix that implements the corrected behavior - apache/maven#8488 — MNG-6787 (original bug report, 2019) -- 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]
