slawekjaranowski commented on code in PR #1691: URL: https://github.com/apache/maven-site/pull/1691#discussion_r4295213262
########## content/markdown/guides/introduction/introduction-to-profiles.md: ########## @@ -111,7 +113,11 @@ The activation occurs when all the specified criteria have been met. ##### Active by default Boolean flag which determines if the profile is active by default. Is `false` by default. -This flag is only evaluated if no other profile is explicitly activated via command line, `settings.xml` or activated through some other activator. Otherwise, it has no effect. + +The suppression behavior differs depending on where the profile is defined: + +- **POM profiles** (`pom.xml`): an `activeByDefault` profile is suppressed as soon as any other profile in the same POM becomes active, whether via explicit `-P` or via a condition activator (file, property, JDK, OS). +- **External profiles** (`settings.xml`): an `activeByDefault` profile is only suppressed when another profile is explicitly requested via `-P` / `--activate-profiles`. A condition-based POM profile activating does **not** suppress external `activeByDefault` profiles. This asymmetry is intentional: external profiles typically carry environment configuration (repositories, credentials) that should remain active regardless of which build-variant POM profile is triggered by the environment. Review Comment: As I know profile defined in `settings.xml` with `activeByDefault` are not deactivated in any condition. -- 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]
