[MNG-3614] settings.xml active profiles executed AFTER project profiles have been loaded and activated/not activated

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Duplicate
• Affects Version/s: 2.0.9
• Component/s: Inheritance and Interpolation, Profiles, Settings
• Environment: Solaris 5.10, ubuntu hardy x64
• Assignee: Benjamin Bentmann
• Reporter: Donald Abrams
• Created: 04/Jun/08 09:48
• Updated: 24/Mar/09 09:50
• Resolved: 24/Mar/09 09:50

Description

If you have the following settings.xml in ~/.m2:

<?xml version="1.0" encoding="UTF-8"?>
<settings>
  <profiles>
    <profile>
      <id>userSettings</id>
      <activation>
        <activeByDefault/>
      </activation>
      <properties>
        <someproperty>true</someproperty>
      </properties>
    </profile>
  </profiles>
  <activeProfiles>
    <activeProfile>userSettings</activeProfile>
  </activeProfiles>
</settings>

and another child pom.xml somewhere down the line has a profile with an activation like this:

<project xmlns="http://maven.apache.org/POM/4.0.0">
  <modelVersion>4.0.0</modelVersion>
  <profiles>
    <profile>
    	<id>with-something</id>    
    	<activation>
       		<activeByDefault>false</activeByDefault>
       		<property>
       			<name>someproperty</name>
       			<value>true</value>
       		</property>
    	</activation>
    </profile>
  </profiles>    
</project>

During run-time, the profile with-something will load before userSettings. This causes with-something to be incorrectly not activated (as the property someproperty does not exist). This can be seen with mvn help:active-profiles.

I know why this is true, but it is non-intuitive and one would expect settings.xml profiles to be loaded before anything else.

Issue Links

• duplicates: MNG-2276 profile activation by property doesn't work with properties defined in settings.
• relates to: MNG-4088 [regression] settings.xml profiles are executed after project profiles