The order in which profiles are activated is currently random.
Say you have two profiles:
and you run
on any pom, then then <properties> section at the bottom will
The same happens if you specify '<activeProfiles><activeProfile>default</..></..>' and run with 'mvn -Poverride'.
This breaks overriding settings since the merge order is random because DefaultProfileManager uses
a HashMap to add active profiles, and HashMap iterators are random.
Proposed fix is to use a LinkedHashMap.