Properties from profiles.xml are not replaced when builing in parent module
Contradiction between the documentation and Maven's behavior related to profile-activation with multiple criteria
Profile activated accidentially
Last Sunday 9:17 PM
Order of plugin execution does not match order of definition in profile
Maven should evaluate profiles per lifecycle
Allow multiple profile activation properties.