As Maven executions set a value for the TARGET_PLATFORM_VERSION value, this property is not overriden by the maximum profile.
Maven order to set properties is
- look a -D... to set property, if not found
- look at active profiles to set property, if not found
- look at default value of property to set it
This makes that in mvn execution for tests, the TARGET_PLATFORM_VERSION is set to minimal is CI jobs, whereas with using the -Pmaximun profile, we expect maximum.
This is a critical issue since it caused hours of confusions to debug on 4.0.x branch.