[MNG-4735] File-based profile activation behaves differently in Maven 3

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Not A Problem
• Affects Version/s: 3.0-beta-1
• Component/s: Profiles
• Environment: Ubuntu 10.04 64-bit, Windows XP 32-bit, Windows 7 64-bit; Java 6
• Assignee: Benjamin Bentmann
• Reporter: Ryan Stewart
• Created: 19/Jul/10 13:49
• Updated: 19/Jul/10 14:12
• Resolved: 19/Jul/10 14:12

Description

I have a project with parent and child poms. The child pom has a profile that is activated by file existence. When running a multimodule build in the directory of the parent pom, the profile fails to activate when it should. Under Maven 2, the profile activates as expected. Example poms that demonstrate the problem are below. Put the first pom in the root of the project. Put the second pom in a subdirectory named "child". Then, in the project root, run "mvn antrun:run". With Maven 2, the output will be "profile property value". Under Maven 3, it will be "default property value".

Note that the problem is unrelated to the antrun plugin. I'm just using it to demonstrate the behavior.

pom.xml

<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
         xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
    <modelVersion>4.0.0</modelVersion>
    <groupId>com.foo</groupId>
    <artifactId>parent</artifactId>
    <packaging>pom</packaging>
    <version>1.0-SNAPSHOT</version>
    <modules>
        <module>child</module>
    </modules>
</project>

child/pom.xml

<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
         xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
    <modelVersion>4.0.0</modelVersion>
    <artifactId>child</artifactId>
    <packaging>jar</packaging>
    <parent>
        <groupId>com.foo</groupId>
        <artifactId>parent</artifactId>
        <version>1.0-SNAPSHOT</version>
    </parent>
    <properties>
        <test.property>default property value</test.property>
    </properties>
    <build>
        <plugins>
            <plugin>
                <artifactId>maven-antrun-plugin</artifactId>
                <version>1.3</version>
                <executions>
                    <execution>
                        <id>default-cli</id>
                        <goals>
                            <goal>run</goal>
                        </goals>
                        <configuration>
                            <tasks>
                                <echo message="Property value: [${test.property}]"/>
                            </tasks>
                        </configuration>
                    </execution>
                </executions>
            </plugin>
        </plugins>
    </build>
    <profiles>
        <profile>
            <id>change-property-value</id>
            <activation>
                <file>
                    <exists>child/pom.xml</exists>
                </file>
            </activation>
            <properties>
                <test.property>profile property value</test.property>
            </properties>
        </profile>
    </profiles>
</project>

Issue Links

• is related to: MNG-2363 <profile><activation><file><exists/> does not work in a multi-project build