[MSHADE-440] Expanded properties in profiles in DRP

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Feedback Received
• Assignee: Unassigned
• Reporter: Niels Basjes
• Created: 24/Mar/23 22:04
• Updated: 05/Nov/23 10:14
• Resolved: 05/Nov/23 10:14

Description

If you have a profile with the ${project.basedir} in the configuration of a plugin IN that profile.

Then when you run maven-shade with that profile active the  ${project.basedir}  will be expanded to the full value in some places of the generated DRP.

If you have something like this in the pom.xml 

  <profiles>
    <profile>
      <id>testProfile</id>
      <properties>
        <prop>CHECK Inside profile ${project.basedir}.</prop>
      </properties>
      <build>
        <plugins>
          <plugin>
            <groupId>org.apache.maven.plugins</groupId>
            <artifactId>maven-clean-plugin</artifactId>
            <executions>
              <execution>
                <id>CHECK Inside profile ${project.basedir}.</id>
                <configuration>
                  <testOutputDirectory>CHECK Inside profile ${project.basedir}.</testOutputDirectory>
                </configuration>
              </execution>
            </executions>
          </plugin>
        </plugins>
      </build>
    </profile>
  </profiles>

then the DRP will have the project.basedir value replaced with the actual path.
This ONLY happens if it is in an profile that was active during while shade was running.

 

Issue Links

• is caused by: MNG-7750 Interpolated properties in originalModel in an active profile.
• links to: GitHub Pull Request #183